Error · 403

ip_not_allowed

This token may not be used from this IP address

What happened

This token is IP-restricted and the request came from an address outside its allowlist.

What to do

Call from an allowed address, or widen the allowlist in the client area.

The endpoint's reference page names the scope it needs — the chip beside its method.
The scope table says what each one grants.
Mint the replacement — scopes are fixed at creation, so this is a new token rather than an edit to the old one.

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
origin_not_allowed — Requests from this origin are not accepted
suspended — This service is suspended
access_blocked — This request could not be completed

Back to the full error reference

403 application/problem+json

{9 keys}

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

:"This token may not be used from this IP address",

:403,

:"This token is IP-restricted and the request came from an address outside its allowlist.",

:"ip_not_allowed",

:"/api/v1/…",

:"req_01hxa3b4c5d6e7f8g9h0j1k2m3",

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

:{2 keys}

:"…",

:"Call from an allowed address, or widen the allowlist in the client area."

}

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 === 'ip_not_allowed') {
  // Call from an allowed address, or widen the allowlist in the client area.
}

What happened

What to do

Other 403 responses