Skip to main content

APIE support codes — Generic API, validation and shared resources

What each of the 47 APIE codes means, and what to do about it.

J
Written by Jean-Baptiste COULON--CHABAGNO

Everything the API owns before a product does: the shape of your request, your account and your organisation, quotas, sessions and the API's own failures.

Find your code below — there are 47 of them. The digit between the letters and the dash says who can act on it: 1 is something you can change, 2 and 9 are Quavern's to fix, 3, 4 and 5 are decisions about access, 6 and 7 mean the service is in maintenance or has moved, and 8 points at the device or the network. APIE uses 1, 2, 6. The shape of a code is explained in How to read a Quavern support code.

Class 1 — Your request or your action

Check what you sent and the state of the account: the request itself, a quota, or the object it names. Correcting that and trying again is normally the whole fix.

APIE1-0404 — not_found

What it means. Nothing is served at the route that was called, or the object its URL names does not exist.

This one carries the generic HTTP status 404.

What to do. Check the path, and check the identifier inside it.

APIE1-0405 — method_not_allowed

What it means. The HTTP method used is not one this route accepts.

This one carries the generic HTTP status 405.

What to do. Check the route's documented methods.

APIE1-0415 — unsupported_media_type

What it means. The media type sent is not one Quavern handles on this route.

This one carries the generic HTTP status 415.

What to do. Use one of the forms the documentation lists for this route.

APIE1-0429 — rate_limited

What it means. Requests arrived faster than Quavern accepts here. There is nothing wrong with what you sent.

This one carries the generic HTTP status 429.

What to do. Wait, then try again more slowly. Honour the Retry-After header when the response carries one.

APIE1-1001 — validation_error

What it means. One or more of the fields in the request did not pass validation. Quavern refused the whole request before it changed anything.

What to do. Read the details object in the response: it names the fields that failed.

APIE1-1002 — invalid_json

What it means. Quavern refused the JSON body: what arrived is not in the form this route accepts.

APIE1-1003 — json_required

What it means. The request cannot go ahead without the JSON body.

APIE1-1004 — payload_too_large

What it means. The request body is larger than this route accepts.

What to do. Send something smaller, or split it into several requests.

APIE1-1005 — confirmation_required

What it means. The request cannot go ahead without an explicit confirmation.

APIE1-1006 — account_exists

What it means. The account is already in the state the request asked for, so Quavern did nothing rather than do it twice.

What to do. Nothing is broken. Read the current state before repeating the step.

APIE1-1007 — account_not_found

What it means. The request named the account, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1008 — unknown_service

What it means. The service named is not one Quavern recognises.

What to do. Use one of the values the documentation lists.

APIE1-1009 — organization_required

What it means. The request cannot go ahead without the organisation it applies to.

APIE1-1010 — organization_not_found

What it means. The request named the organisation, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1011 — organization_forbidden

What it means. Quavern refused the action on the organisation. The caller is known to Quavern; it does not hold the right to do this.

APIE1-1012 — membership_not_found

What it means. The request named the membership, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1013 — membership_forbidden

What it means. Quavern refused the action on the membership. The caller is known to Quavern; it does not hold the right to do this.

APIE1-1014 — owner_required

What it means. Only the owner of the organisation may do this, and the account making the request is not the owner.

What to do. Ask the owner to do it, or to transfer ownership first.

APIE1-1015 — seat_limit_reached

What it means. The number of seats in the organisation already sits at the highest Quavern allows on this account or this plan, so one more was refused.

What to do. Remove one you no longer need, or move to a plan with a higher ceiling.

APIE1-1016 — current_session

What it means. Quavern has not published what this code means. Its name does not settle it, and this page will not guess — the slug names a thing, not a failure: it does not say whether the session in question may not be revoked, may not be replaced, or something else.

What to do. Quote the code to support at [email protected], with the time and what you were doing, and you will be told what it means.

APIE1-1017 — session_not_found

What it means. The request named the session, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1018 — token_not_found

What it means. The request named the token, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1019 — membership_exists

What it means. The membership is already in the state the request asked for, so Quavern did nothing rather than do it twice.

What to do. Nothing is broken. Read the current state before repeating the step.

APIE1-1020 — organization_over_capacity

What it means. The capacity of the organisation is used up — for the period in progress, or for what this plan allows.

What to do. Wait for the period to roll over, or move to a plan that allows more.

APIE1-1021 — account_deletion_blocked_subscription

What it means. Quavern will not carry out the account deletion: an active subscription stands in the way.

What to do. Settle what is in the way first, then ask again.

APIE1-1022 — account_deletion_blocked_owner

What it means. Quavern will not carry out the account deletion: the account still owns an organisation.

What to do. Settle what is in the way first, then ask again.

APIE1-1023 — account_deletion_blocked_billing

What it means. Quavern will not carry out the account deletion: unsettled billing stands in the way.

What to do. Settle what is in the way first, then ask again.

APIE1-1024 — ownership_transfer_target_invalid

What it means. The account named as the new owner is not one Quavern will accept here: the conditions this asks for are not met.

APIE1-1025 — ownership_transfer_conflict

What it means. Another change touching the transfer of ownership was in flight, so Quavern refused this one rather than let the two overwrite each other.

What to do. Reload the current state and start the change again.

APIE1-1026 — account_deletion_conflict

What it means. Another change touching the account deletion was in flight, so Quavern refused this one rather than let the two overwrite each other.

What to do. Reload the current state and start the change again.

APIE1-1027 — ownership_transfer_blocked_subscription

What it means. Quavern will not carry out the transfer of ownership: an active subscription stands in the way.

What to do. Settle what is in the way first, then ask again.

APIE1-1028 — email_unavailable

What it means. The e-mail address cannot be used here: something else already holds it, or Quavern does not allow it on this account.

What to do. Choose another value.

APIE1-1029 — mfa_already_enabled

What it means. The second factor is already in the state the request asked for, so Quavern did nothing rather than do it twice.

What to do. Nothing is broken. Read the current state before repeating the step.

APIE1-1030 — mfa_not_enabled

What it means. The second factor is not switched on for this account, and this route does not work without it.

What to do. Switch it on from the account page first.

APIE1-1031 — mfa_setup_required

What it means. The request cannot go ahead without two-step verification set up on the account.

APIE1-1032 — memory_not_found

What it means. The request named the memory, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1033 — folder_not_found

What it means. The request named the folder, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1034 — share_not_found

What it means. The request named the share, and Quavern holds no record of it: either it never existed, it was deleted, or it belongs to another account.

What to do. Check the identifier you sent, then check you are signed in as the account that owns it.

APIE1-1035 — folder_exists

What it means. The folder is already in the state the request asked for, so Quavern did nothing rather than do it twice.

What to do. Nothing is broken. Read the current state before repeating the step.

APIE1-1036 — memory_capacity_exceeded

What it means. The memory capacity is used up — for the period in progress, or for what this plan allows.

What to do. Wait for the period to roll over, or move to a plan that allows more.

APIE1-1429 — quota_exhausted

What it means. The quota is used up — for the period in progress, or for what this plan allows.

What to do. Wait for the period to roll over, or move to a plan that allows more.

Class 2 — Quavern's server or one of its dependencies

Nothing you did caused it. Wait a moment and try again. If it keeps happening, send support the code and the time — that is what lets the incident be found in the logs.

APIE2-0502 — bad_gateway

What it means. The connection from the edge to the API failed. The failure is on Quavern's side, not in what you sent.

This one carries the generic HTTP status 502.

*From the registry:* Generated by nginx on the API hosts when the application is unreachable (marl/deploy/quavern-errors/*.json); registered so the edge and the application can never answer the same condition with two codes.

APIE2-0503 — service_unavailable

What it means. The API service did not answer, and this route cannot be served without it.

This one carries the generic HTTP status 503.

APIE2-0504 — gateway_timeout

What it means. The connection from the edge to the API did not answer within the time Quavern is willing to wait.

This one carries the generic HTTP status 504.

APIE2-1500 — internal_error

What it means. The API's own handling of this request failed. The failure is on Quavern's side, not in what you sent.

APIE2-1501 — storage_error

What it means. The storage layer failed. The failure is on Quavern's side, not in what you sent.

Class 6 — Declared maintenance

Quavern is inside a maintenance window it announced. Check https://status.quavern.net and try again once the window closes.

APIE6-1503 — maintenance

What it means. Quavern has declared a maintenance window and is refusing this route for its duration.

Still stuck

Write to [email protected] with the code, the reason, the time with its time zone, and the route you called. Never send a password, a token, an API key or full card details — support will never ask for any of them.

Quavern help reference: support-codes-apie/en

Did this answer your question?