DocumentationAPI v1
HTTP 401 · Key and access

missing_token

No key sent

HTTP status401
Retry Nonot without a change
FamilyKey and access

What the API answers

No API token was provided.

The message stays in English, like every API response: branch your script on error.code, which never changes.

What to do

Send the key in the Authorization header, with or without Bearer. For a script that cannot set a header, such as screenshot-basic, add ?apiKey= to the URL.

Key and access. The API key was missing, unknown, revoked, used from an address it does not allow, or lacks the permission for the call. Fixed on the key, or in the configuration that sends it.

Full response

JSON
{
    "status": "error",
    "error": {
        "code": "missing_token",
        "message": "No API token was provided.",
        "docs": "https://aperture-app.preview.moncompanion.cloud/docs/errors/missing_token"
    },
    "meta": {
        "request_id": "01K2R7M8QF3V9XZ4B6NCDT0YAH",
        "api_version": "v1",
        "duration_ms": 12,
        "timestamp": "2026-10-27T14:32:08+00:00"
    }
}

The meta values are a sample. meta also carries app_version and commit, and a refusal may add error.details with the value at fault.

Codes of the same family

HTTP Code What to do Retry
401 missing_tokenNo key sent Send the key in the Authorization header, with or without Bearer. For a script that cannot set a header, such as screenshot-basic, add ?apiKey= to the URL. No
401 invalid_tokenUnknown key The key sent does not exist. Copy it again in full, with no space or line break, from where you kept it when it was created. No
401 token_revokedRevoked key This key was revoked. Create a new one in the customer space and replace it in the resource that sends it. No
403 ip_not_allowedAddress not allowed The key is limited to some IP addresses. Add the address of the calling server to its list, or lift the restriction. No
403 insufficient_scopeKey lacks the scope The key lacks the scope this call needs, for instance upload-video to send a video. Add it, or use a key that has it. No
403 feature_not_enabledFeature not enabled This feature is not enabled for your organisation. The platform operator enables it: error.details.feature says which one to ask for. No
403 forbiddenAction not allowed Your account or your key is not allowed to do this in the organisation. Ask an owner for the permission. No
401 upload_ticket_invalidUpload ticket not valid The ticket is unknown, expired or already used. Ask your server for a new one: a ticket works once, within the 60 seconds after it was issued. No

Every error code