---
title: "Forbidden"
description: "The API key's account does not own the envelope, recipient, document or deliverable you requested. Use a key from the account that created it."
canonical: "https://signatureapi.com/docs/v1/errors/forbidden"
source: "https://signatureapi.com/docs/v1/errors/forbidden.md"
last_verified_api_version: "1.18.0"
last_modified: "2026-11-18T11:41:57Z"
---

# Forbidden

The API key's account does not own the envelope, recipient, document or deliverable you requested. Use a key from the account that created it.

_Last verified against API version 1.18.0._

## What Happened

The resource exists, but it belongs to a different account than the API key you used. The public API returns this error when an ID in the URL points to an envelope, recipient, document or deliverable owned by another account.

A missing or unknown API key, or a blocked account, returns [Invalid API Key](https://signatureapi.com/docs/v1/errors/invalid-api-key) instead.

## Example response

```json 403 Forbidden (application/problem+json)
{
  "type": "https://signatureapi.com/docs/v1/errors/forbidden",
  "title": "Forbidden",
  "status": 403,
  "detail": "You are not allowed to access this envelope"
}
```

## How to Fix

- Use the API key of the account that created the resource. If you work with several accounts, check which one the key belongs to.
- Check that the ID in the URL is the one you meant.
- A test key cannot read a live resource and a live key cannot read a test resource. That mismatch returns [Test/Live Mode Error](https://signatureapi.com/docs/v1/errors/mode-error).

Still stuck? [Contact support](https://signatureapi.com/support).
