Start free →

Reference

Error codes

Every error the API answers and the dashboard shows carries a stable code; an API answer also carries doc_url, the link to its line below. Each line says what the code means and leads to its full entry — its most frequent cause, what to do and who can do it — on the page of its family.

What an error answer carries

  • error — a sentence for a person, in English. It may change: never test it in code.
  • code — the stable identifier. Test this one.
  • doc_url — the link to the code’s section on this page, on your deployment’s own address.
  • field — for validation_failed, the field of the request that was refused, as a dotted path.
  • refusal — for a call the gateway refused, when helpful refusals are on: what was blocked, why, the rule and its owner, the compliant options, in the caller’s language.

A code not listed here belongs to one screen or one route, and its message says what to do.

Access and sign-in

Every entry of this family, in full

  • session_required — The request carries no valid session: it reached a dashboard route without being signed in.
  • session_expired — The session is older than the longest a session may last on this deployment, so it is refused even though it is still refreshed.
  • mfa_challenge_required — Your account has two-factor authentication on, and this session has not completed it yet.
  • workspace_required — The request does not name the workspace it is for.
  • forbidden — Your account is signed in, but it has no access to what the request names.
  • not_a_member — You are signed in, but not as a member of the workspace this request names.
  • admin_required — This action is reserved for the owners and admins of the workspace.
  • owner_required — This action is reserved for the owners of the workspace.
  • mfa_required_by_workspace — The workspace asks every member to sign in with two-factor authentication.
  • mfa_enrolment_required — The workspace asks its owners and admins to have two-factor authentication before they change roles, retention, API keys, the governance mode or rules.
  • membership_lookup_failed — Azoth could not check your membership, so it refused rather than guess.
  • csrf_origin_mismatch — The request came from a web address the app does not recognise, so it was refused to protect you from cross-site requests.
  • second_admin_required — This action needs a second person to approve it, and the workspace has a single owner or admin.
  • reviewer_must_differ_from_declarant — A mandate is reviewed by someone other than the person who declared it.
  • email_not_verified — Your e-mail address is not confirmed yet.
  • captcha_failed — The anti-robot check of the form did not pass.
  • invalid_credentials — The e-mail address and password do not open an account.
  • email_domain_not_accepted — Sign-up is refused for addresses of disposable-mail services.
  • professional_use_required — Azoth OS is offered only to businesses and professionals: an account is opened only with the declaration that it is for a business or professional activity.
  • weak_password — The sign-up refused the password as too weak.
  • support_access_required — Azoth’s staff cannot open access to the data of this workspace without an owner’s approval.
  • permission_denied — Your role in this workspace does not grant the permission this action needs.
  • invitee_already_member — An invitation adds a person to a workspace; it never changes the role of someone who is a member already. This address is a member’s, so no invitation was created.
  • invite_role_not_allowed — An invitation grants its role when it is accepted, under the authority of whoever sent it: any workspace role but owner. The role asked for is not one of them, so no invitation was created.
  • already_a_member — You opened an invitation to a workspace you are a member of already. It is used up and changed nothing: your role stays as it is.
  • org_invitee_already_member — An invitation adds a person to an organisation; it never changes the role of someone who is a member already. This address is a member’s, so no invitation was created.
  • already_an_org_member — You opened an invitation to an organisation you are a member of already. It is used up and changed nothing: your role stays as it is.
  • feature_disabled — The module this route belongs to is not enabled on this deployment.
  • assistant_disabled — The workspace has turned its assistant off: nothing answers its questions — in the app, in a chat app or through the API.
  • origin_not_allowed — A browser sent this request from a page of another site. The MCP endpoints answer an MCP client, or a page of this deployment — never a page of another site, which could otherwise reach them through the browser of a person who opens it.
  • capability_off — This feature runs on this deployment and the workspace’s plan includes it, but the workspace has it off — its own choice.
  • cannot_remove_self — Nobody removes themselves from a workspace here: an owner or admin removes the other members.
  • last_owner — A workspace always keeps one owner at least: its last owner can be neither removed nor given another role.
  • org_admin_required — Only an admin of an organisation adds a workspace to it.
  • owner_mfa_first — Requiring two-factor authentication of the workspace’s members needs it on your own account first.
  • invite_daily_limit — Too many invitation e-mails were sent today — to this address, by you or from this workspace — so this one was not sent.
  • sso_required — The organisation of this address signs its members in through single sign-on: a password sign-in, sign-up or reset is refused.
  • member_not_found — No member of this workspace has this id.
  • invite_already_accepted — This invitation was accepted already: an invitation is used once.
  • invite_expired — This invitation has expired and can no longer be accepted.
  • invite_email_mismatch — This invitation is for another e-mail address than the signed-in account’s: only the invited address can accept it.
  • invite_no_longer_valid — This invitation no longer holds: the person who sent it can no longer grant the role it offers.
  • invite_already_pending — An invitation already waits for this address, so no second one was created.
  • account_email_missing — The signed-in account has no e-mail address, and this action needs one: an invitation is accepted by its address, a test e-mail is sent to it.
  • org_role_protected — In an organisation, nobody changes their own role, and the owner’s role is neither changed nor removed.
  • signup_failed — The account could not be created, for a reason the sign-up does not give.
  • only_workspace — This is the only workspace of your account, so it is not deleted on its own.

API keys and the person a call is for

Every entry of this family, in full

  • api_key_invalid — The Azoth API key sent with the call matches no active key.
  • api_key_missing — The call carries no Azoth API key.
  • api_key_scope_denied — The key is valid, but it is limited — to scopes (the parts of the API it may call), to connectors or to environments — and this call falls outside those limits. At ingest, the answer’s dimension says which limit refused it: connector or environment.
  • api_key_name_taken — A live key of the workspace already has the name asked for: two live keys of one workspace never share a name.
  • api_key_role_denied — The key is valid, but its role — read, write or admin — is below what this route needs: a read key cannot call a route that writes, and an export of the workspace’s settings needs an admin key.
  • ip_not_allowed — The key is valid, but the call came from an address outside the workspace’s IP allowlist: the workspace accepts its API keys only from the addresses it lists.
  • on_behalf_of_not_allowed — This call was blocked: its API key may not name the person it is for.
  • human_identity_required — This call was blocked: it does not name the person it is for.
  • identity_unavailable — This call was blocked: the person it is for could not be checked.
  • invalid_on_behalf_of — The X-Azoth-On-Behalf-Of header is not an identifier of a person Azoth can read.
  • key_not_bound_to_agent — The MCP gateway answers only an API key bound to one agent — the agent whose mandate decides what it may call — and this key is bound to none.
  • invalid_key_identity — A personal key always speaks for its owner: it cannot also name other people.

Model providers and the trial key

Every entry of this family, in full

Checks at the gateway

Every entry of this family, in full

  • policy_blocked — This call was blocked by a rule of your workspace.
  • sovereignty_blocked — This call was blocked by the data-residency policy.
  • jurisdiction_blocked — This call was blocked by the law that applies to it.
  • kill_switch_active — This call was blocked: the emergency stop is on.
  • kill_switch_unavailable — This call was blocked: the emergency-stop check could not run.
  • data_exfiltration_blocked — This call was blocked: the message contains secret content.
  • prompt_injection_blocked — This call was blocked: the message reads as an attempt to override the model’s instructions.
  • redaction_failed — This call was blocked: its personal data could not be masked.
  • governance_error — This call was blocked: the governance checks could not run.
  • loop_detected — This call was blocked: the same call repeated in a loop.
  • tenant_concurrency_limit — This call was blocked: too many calls are running at once.
  • human_review_required — This call is waiting for a person to approve it.
  • human_review_not_resumable — This call was blocked: it needs a human approval, and it cannot be held.
  • approval_expired — This call was not run: its approval expired.
  • ungrounded_answer — This answer was not returned: its sources do not support enough of it.
  • grounding_review_required — This answer is waiting for a person to check it.
  • grounding_requires_complete_answer — This call was blocked: its answer must be checked before it is sent.
  • pending — The approval this request waits for has not been decided yet: the held call has not run, the held answer is not handed over.
  • rejected — A reviewer rejected the approval this request waits for: the held call will never run, the held answer will never be handed over.
  • already_executed — The held call of this approval has run already: an approval runs its call once.
  • already_released — The held answer of this approval was handed over already: it is handed over once, then erased.
  • not_requester — Only the API key that sent a held call can run it once it is approved.
  • idempotency_key_invalid — The Idempotency-Key header is empty, too long, or holds a character it may not hold.
  • idempotency_key_reused — A call already used this Idempotency-Key within the hour with another body: one key names one call.
  • idempotency_key_in_progress — The first call with this Idempotency-Key has not answered yet: it is never run a second time meanwhile.
  • idempotency_replay_unavailable — The first call with this Idempotency-Key was answered, but its answer was not kept: a retry gets neither that answer nor a second model call.
  • approval_pending — The step this agent execution paused on still waits for a reviewer’s decision: nothing was run.
  • approval_rejected — A reviewer rejected the step this agent execution paused on: the step will not run, and the execution cannot be resumed.
  • approval_not_found — This agent execution has no approval request left to resume it with.
  • already_resumed — The approved step of this execution has run already: an approval runs its step once.
  • execution_not_found — No agent execution has this id in this workspace.
  • not_awaiting_approval — This agent execution is not paused for an approval, so there is nothing to resume.
  • agent_plan_invalid — The plan the agent’s planner made did not pass its checks, so nothing ran. The answer’s details lists what failed.

Mandates: systems and agents

Every entry of this family, in full

  • usecase_unresolved — This call was blocked: it is not tied to any mandate.
  • usecase_not_approved — This call was blocked: its mandate is not approved yet.
  • usecase_divergence — This call was blocked: it does not match its approved mandate.
  • mandate_suspended — This call was blocked: its mandate is suspended.
  • mandate_expired — This call was blocked: its mandate has ended.
  • usecase_prohibited — This call was blocked: its mandate is classified as a prohibited practice.
  • ai_act_class_required — A mandate is approved only with its EU AI Act risk class.
  • mandate_incomplete — A mandate is approved only once it names an accountable person and an end date.
  • mandant_not_member — The person who answers for a mandate must be a member of the workspace.
  • mandate_end_in_past — The end date given for the mandate has already passed.
  • mandate_end_too_far — A mandate lasts three years at most.
  • mandate_delegation_exceeded — The mandate of a sub-agent goes beyond the mandate of its parent agent.
  • mandate_required — The request names no mandate.
  • mandate_not_found — The mandate named is not in this workspace.
  • usecase_not_found — This system does not exist in this workspace.
  • agent_not_found — No agent of this workspace has this id.
  • agent_archived — The agent is archived: it is read-only, and nothing runs for it — no execution, no tool call, no new mandate, key or red-team campaign.
  • usecase_archived — This call was blocked: its mandate is archived.
  • usecase_not_archived — This mandate is not archived, so there is nothing to unarchive.
  • usecase_is_default — This mandate is the workspace’s default use case, so it is not archived.
  • redteam_campaign_running — A red-team campaign is still testing this mandate, so it is not archived yet.
  • human_reviewer_required — Approving or rejecting a system is a person’s act, signed in to the dashboard: an API key may declare a system, never review it.
  • mcp_tool_changed — The MCP tool you reviewed is no longer the definition the catalogue holds, so your review was not applied.
  • identity_missing — An agent receives a mandate only once it has an identity: a person who answers for it.
  • identity_revoked — This agent’s identity is revoked: it can no longer be changed.
  • parent_not_found — The parent named is not another agent of this workspace.
  • parent_loop — This parent would make a loop of agents: an agent never delegates to one of its own ancestors.
  • mcp_tool_not_approved — The mandate names an MCP tool the catalogue has not approved.
  • version_conflict — Another version of this mandate was created at the same moment, so this one was not saved.
  • name_taken — An MCP server with this name is already in the catalogue.
  • prohibited_practice_requires_exception — A system with a blocking flag is not approved as it stands: it is rejected, or approved with a documented exception.
  • exception_requires_justification — A documented exception needs a written justification of 200 characters at least.
  • exception_requires_attachment — A documented exception needs the reference of the document that supports it.
  • redteam_gate — A high-risk system is approved only after a recent red-team campaign that reached the workspace’s threshold, or under a waiver in force.
  • mandate_models_empty — A mandate’s list of models names one model at least.
  • mandate_models_exist — This mandate already has its list of models: it grows only from a comparison run that held.
  • mandate_models_not_active — This mandate’s list of models is not in force, so nothing can be added to it.
  • replay_not_validated — A model is added to a mandate only from a comparison run that completed and passed.
  • unpriced_model — This model has no price, so its cost could not be capped: it is never called.
  • no_category — None of the categories chosen applies to this target.
  • nothing_to_replay — This campaign has no failed probe to run again.
  • source_running — The campaign whose failed probes were asked for again has not finished yet.
  • library_changed — The probe library has changed since that campaign, so its probes cannot be run again as they were.
  • already_imported — This file was already imported for this system.
  • not_json — The results file is not JSON.
  • unrecognised_format — The file is neither a Giskard scan (to_json) nor the azoth.redteam.import/1 format.
  • invalid_results — The file’s results do not match their format: the answer’s error says where.
  • ran_in_future — The file says its run happened in the future.
  • agent_not_archived — This agent is not archived, so there is nothing to unarchive.

Budgets, plan limits and public systems

Every entry of this family, in full

The applicable law and retention

Every entry of this family, in full

Waivers and options of a refusal

Every entry of this family, in full

Proof: holds, dossiers and timestamps

Every entry of this family, in full

Incident mode

Every entry of this family, in full

Model changes and the portfolio

Every entry of this family, in full

Any request: validation and server failures

Every entry of this family, in full

  • validation_failed — The request’s body or parameters do not match what the route accepts, so nothing was done. The answer’s error describes the problem and field names the field, when there is one.
  • internal_error — The request failed on Azoth’s side, for a reason the answer does not give: nothing in the request was at fault. The failure is recorded for Azoth’s team.
  • not_found — Nothing the request names exists in this workspace — or it exists, but this caller may not read it.
  • service_unavailable — Azoth could not reach its database, so nothing was done and nothing was recorded.
  • unknown_tool — No insight tool has this name. The answer’s tools lists the names that exist.
  • not_configured — This deployment lacks a setting the request needs — a secret, a vendor’s account or keys — so nothing was done. Trying again changes nothing until it is set.
  • migration_missing — This feature needs a database update that is not applied yet, so nothing was done.
  • replay_unavailable — A request cannot be sent again by Azoth: Azoth keeps a hash of each prompt, never the prompt itself.
  • action_not_offered — This action is not offered for this item of the queue.
  • item_not_waiting — This item no longer waits in the queue.
  • not_allowed — You may not act on this item of the queue.
  • delegate_to_self — An item is not delegated to yourself.
  • delegate_not_allowed — The member chosen may not act on this item, so it cannot be delegated to them.
  • worker_secret_invalid — A scheduled job or an internal route of the deployment was called without its secret, so nothing ran.
  • already_exists — What the request would add exists already: the name, address or value it gives is taken, so nothing was added.
  • operation_in_progress — The same operation is already running for this workspace, so this request did nothing.
  • method_not_allowed — The route does not take this HTTP method; the answer’s Allow header names the one it takes.
  • integration_not_connected — The integration this action needs — GitHub, Slack, Microsoft Teams, single sign-on or a model endpoint — is not set up for this workspace.
  • integration_failed — The service of an integration — GitHub, Slack, Microsoft Teams — refused or failed the request Azoth sent it, so nothing was done. The answer gives its HTTP status (vendorStatus) and its own error code (vendorCode), never its text.

Support: tickets and access

Every entry of this family, in full

Single sign-on, chat apps and connectors

Every entry of this family, in full

  • sso_oidc_unavailable — The identity provider of this address could not be reached, so single sign-on could not start or complete.
  • sso_domain_unverified — Single sign-on cannot be required for a domain the workspace has not verified it owns.
  • sso_provider_required — Single sign-on cannot be required while no identity provider is enabled for the workspace.
  • sso_type_change — This workspace already has a SAML identity provider: an OIDC provider cannot be saved beside it.
  • oidc_client_secret_required — An OIDC identity provider is saved with its client secret.
  • oidc_issuer_invalid — The issuer is not a public https address an identity provider can use, so the provider was not saved.
  • oidc_issuer_multi_tenant — This issuer serves many organisations, so it cannot sign in the members of one workspace.
  • oidc_discovery_failed — The identity provider’s discovery document could not be read, so the provider was not saved.
  • oidc_discovery_mismatch — The identity provider’s discovery document names another issuer, or lacks an endpoint, so the provider was not saved.
  • sso_too_many_attempts — Too many single sign-on returns came from this network address in a minute, so this one was not completed.
  • sso_attempt_expired — The sign-in that came back from the identity provider is not one this browser started, or it took too long, so no session was opened.
  • sso_idp_refused — The identity provider came back without signing the person in, so no session was opened.
  • sso_provider_unavailable — The workspace’s single sign-on is not available any more, so the sign-in could not be completed.
  • sso_provider_misconfigured — The workspace’s identity provider settings cannot be used to sign in, so no session was opened.
  • sso_token_exchange_failed — The identity provider refused to complete the sign-in for Azoth, so no session was opened.
  • sso_id_token_invalid — The identity the provider sent could not be verified, so no session was opened.
  • sso_email_domain_mismatch — The identity provider signed the person in with an e-mail address outside the workspace’s verified domain, or with none, so no session was opened.
  • sso_email_unverified — The identity provider did not confirm it verified the e-mail address, so no session was opened.
  • dns_lookup_failed — The domain’s DNS could not be read, so its ownership could not be checked.
  • record_not_found — The TXT record that proves the domain was not found in its DNS.
  • domain_already_verified — Another Azoth workspace has already verified this domain: one domain signs in to one workspace.
  • domain_changed — The single sign-on domain changed while it was being verified, so nothing was recorded.
  • sso_provider_update_failed — The domain is verified, but registering it with the sign-in service failed.
  • sso_provider_delete_failed — The sign-in service did not remove the workspace’s SAML identity provider, so Azoth removed nothing either: single sign-on stays as it was.
  • not_installed — This Slack workspace or Teams bot is not connected to Azoth.
  • chat_identity_mismatch — This chat account is not yours: the e-mail its platform holds for it is not the e-mail of your Azoth account, so nothing was linked.
  • chat_identity_unverified — The chat platform does not give this account’s e-mail, so Azoth cannot tell whose it is: nothing was linked.
  • chat_identity_unavailable — The chat platform could not say whose account this is, so nothing was linked.
  • teams_secret_required — A Teams bot is saved with its client secret.
  • teams_credentials_invalid — Microsoft refused these credentials, so the bot was not saved.
  • teams_app_taken — This Teams bot is already connected to another Azoth workspace.
  • connector_not_available — Connecting an assistant (Claude, ChatGPT) is not included in this workspace’s plan.
  • connectors_disabled — The workspace’s owners or admins turned connected assistants off.
  • missing_token — The connector endpoint was called without an access token.
  • invalid_token — The connector endpoint was called with an access token it does not accept: expired, revoked, malformed or issued for another address.
  • insufficient_scope — The access token does not carry the read access the connector needs.
  • missing_client — The connection request names no client, so the assistant cannot be connected.
  • unknown_client — The connection request names an assistant Azoth does not know.
  • invalid_redirect_uri — The connection request’s return address is not one the assistant declared, so Azoth will not send it there.
  • connector_not_installed — The Inventory Object connector is not installed for this workspace and environment, so nothing was stored.
  • connector_revoked — This connector was uninstalled, so it cannot be approved: an uninstall is never turned back on.
  • connector_governance_failed — The connector’s governance check failed during the test ingestion, so the test row was not stored.
  • repository_not_found — No repository of this workspace’s GitHub connection has this id.

Azoth’s team tools

Every entry of this family, in full