Error · 403

access_blocked

This request could not be completed

What happened

The request was not completed.

What to do

Contact [email protected], quoting the requestId in the response.

The response body carries a recovery object with the same guidance in machine-readable form: recovery.action names the call to make next, and recovery.hint is one sentence a model can act on. Not every code carries one — a 401, for instance, has nothing to recover to but a valid token.

insufficient_scope — This token does not have the required scope
readonly_scope — This token is read-only
not_owned — Not owned by this account
domain_not_owned — Domain not owned by this account
node_not_allowed — That hosting node is not permitted
ip_not_allowed — This token may not be used from this IP address
origin_not_allowed — Requests from this origin are not accepted
suspended — This service is suspended

Back to the full error reference

403 application/problem+json

{9 keys}

:"https://api.inleed.com/errors/access_blocked",

:"This request could not be completed",

:403,

:"The request was not completed.",

:"access_blocked",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

:"2026-08-29T12:34:56.000Z",

:{2 keys}

:"…",

:"Contact [email protected], quoting the requestId in the response."

}

Click a key to copy its jq path.

Handling it

// Branch on code, never on title or detail — those are written for
// humans and may change wording at any time.

if (problem.code === 'access_blocked') {
  // Contact [email protected], quoting the requestId in the response.
}

What happened

What to do

Other 403 responses