The request has no valid token

HTTP status 401

Send an API token in the Authorization header, as Bearer followed by the token. An admin creates tokens under Settings, Developer, API tokens.

From Pro up

The API did not get a token it could use, so it looked nothing up. Most often the Authorization header is missing or not in the form the API reads.

Why you get it

The detail field says which of these happened:

• The request has no Authorization header, or its value does not start with the word Bearer and a space.
• The address carries a token, or a parameter named token, access_token or api_key. The API refuses such a request even when the header is right, because addresses end up in logs.
• We do not recognise the token. It was not copied whole, or its organization has been deleted.
• An admin has revoked the token. Revoking ends a token at once.

A token past its expiry date gets its own code. A valid token that the plan does not allow gets a 403 instead.

What to do

1. Send the token in the header, written as Authorization: Bearer mm_…, and never in the address.
2. Copy the token again from where you saved it. We show a token once, when it is created, and keep only a hash of it, so nobody can show it to you again.
3. If the token was revoked or lost, an admin creates a new one under Settings, Developer, API tokens.

Published 27 October 2026 · Checked 27 October 2026