AB series alongside the HTTP status. The code is the precise reason; the status is the class.
Error reference
The four you will actually hit
AB03: User not allowed to access the resource (403)
AB03: User not allowed to access the resource (403)
The token is valid, but it does not reach this resource.
- Wrong tenant. The token’s
tsg_idnames a different tenant from the one that owns the resource. A token cannot cross a TSG boundary unless an access policy grants it. - Insufficient role. The service account that obtained the token holds a role that does not cover this operation.
- Wrong workspace. The resource belongs to a workspace, and the
workspace_idyou passed points somewhere else.
AB01: Request Validation Error (400)
AB01: Request Validation Error (400)
The body did not match what the endpoint expects. Usually one of:
- a required parameter is missing
- a value has the wrong type, a number where a string belongs
- a value sits outside the allowed set for an enum
AB08: Resource not found (404)
AB08: Resource not found (404)
The path is right and the resource is not there. Two causes dominate:
- A slug was passed where an ID was expected, or the reverse. Configs, integrations and providers take slugs; guardrails, MCP servers, policies and API keys take IDs.
- The resource belongs to a workspace you did not name. Pass
workspace_idas a query parameter onGET, and in the body onPOSTandPUT.
AB07 on a create means the resource already exists. Most creates are not idempotent, so retrying a request that timed out can produce a 409 rather than a duplicate. Check before retrying blindly.Authentication
Most Admin API errors are authentication errors. Start here.

