LIVE_CREDENTIAL_REQUIRED

When it happens

The operation changes the real account (members, invitations, access to a managed account) and was called with a sandbox key. Those changes are not scoped to an environment, so a test key cannot make them.

How to fix it

Call it with a live API key or from the dashboard.

Retry

Not as is: the same request fails the same way. Fix the cause described above, then send the request again, under a new Idempotency-Key if the body changed.

Returned by

The operations where this code is most likely. The list is not exhaustive.

• POST /v1/accounts/{account_id}/invitations
• DELETE /v1/accounts/{account_id}/invitations/{invitation_id}
• PATCH /v1/accounts/{account_id}/members/{member_id}
• DELETE /v1/accounts/{account_id}/members/{member_id}
• PUT /v1/accounts/{account_id}/members/{member_id}/grants/{company_id}
• DELETE /v1/accounts/{account_id}/members/{member_id}/grants/{company_id}
• PATCH /v1/accounts/{account_id}/access-level
• DELETE /v1/accounts/{account_id}/management

Example response

When this error occurs, the API answers 403 Forbidden with a JSON body of this shape:

{
  "type": "https://docs.beel.es/errors/LIVE_CREDENTIAL_REQUIRED",
  "title": "LIVE_CREDENTIAL_REQUIRED",
  "detail": "This operation changes the real account; it requires a live API key or a dashboard session.",
  "instance": "/v1/<resource>",
  "errors": [],
  "success": false,
  "error": {
    "code": "LIVE_CREDENTIAL_REQUIRED",
    "message": "This operation changes the real account; it requires a live API key or a dashboard session.",
    "details": {}
  },
  "meta": {
    "timestamp": "2026-05-21T10:00:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

The type URI is stable and always resolves to this page.

Message

Send the request with Accept-Language: <es|en|ca> to receive the message in your preferred language.

Other errors in this category

Keep exploring