> ## Documentation Index
> Fetch the complete documentation index at: https://docs.deal-pipe.de/llms.txt
> Use this file to discover all available pages before exploring further.

# Errors and limits

> Handle error codes and retry requests deliberately.

## Error format

```json theme={null}
{
  "error": {
    "code": "missing_scope",
    "message": "Missing scope: property:read",
    "requestId": "example-request-id"
  }
}
```

`details` can contain additional information. Log the status, error code, and `X-Request-Id` without recording the secret token.

| HTTP | Meaning and next step |
| - | - |
| 400 | Check JSON, fields, or filters. Read validation details. |
| 401 | Missing, invalid, expired, or revoked token; an inactive creator can also cause this. |
| 402 | Allowance exceeded. Review the reported usage and plan. |
| 403 | Missing scope, restricted object access, or suspended organization. |
| 404 | Record not found or not visible to this request. |
| 429 | Request budget reached. Observe `Retry-After`. |
| 500 | Server error. Keep the request ID for investigation. |

## Rate limits

The default budget is 60 requests per minute per token; individual tokens can have a custom limit. Authenticated responses include `X-RateLimit-Limit`, `X-RateLimit-Remaining`, and `X-RateLimit-Reset`. For `429`, use `Retry-After` as the waiting instruction; do not create a tight retry loop based on the reset header.

Reduce concurrency and group reads appropriately. Retry writes only after checking their outcome. Repeating invalid inputs or requests without the necessary permissions does not resolve them.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.