key_in_query_forbidden

HTTP 400key_in_query_forbiddenAPI key in query string is forbidden

The API key was sent in the query string (e.g. ?api_key=). We treat an existing secret key as leaked and revoke it automatically (publishable mk_pub_ keys are not revoked).

Common causes

• a key in the URL, which ends up in server, proxy and browser logs

What to do

• Create a new key in the dashboard.
• Send the key only in the Authorization: Bearer … header (or X-API-Key).

Retry?	No, the result will be the same unless the request changes.
Billing	0 units.
type	https://maticna.si/docs/errors/key_in_query_forbidden

Example response

HTTP/1.1 400
Content-Type: application/problem+json
X-Request-Id: req_01JB2Q8X6S7T

{
  "type": "https://maticna.si/docs/errors/key_in_query_forbidden",
  "title": "API key in query string is forbidden",
  "status": 400,
  "detail": "The API key was sent in the query string (e.g. ?api_key=). We treat an existing secret key as leaked and revoke it automatically (publishable mk_pub_ keys are not revoked).",
  "instance": "/v1/entities/12345679",
  "code": "key_in_query_forbidden",
  "request_id": "req_01JB2Q8X6S7T"
}

Other errors with status 400

• bad_request · Bad request

All errors