Errors

Intel API error codes and HTTP statuses, from invalid queries and IPv6 to missing keys, exhausted credits and oversized prefixes.

Every error from /v1, /open and /me is a JSON object with a stable code and a human-readable message:

curl https://api.layer3intel.com/open/2001:db8::1

{ "error": { "code": "ipv6_not_supported", "message": "only IPv4 is supported" } }

Read code. message is for people and may change.

Status	`code`	When
400	`invalid_query`	Not an IPv4 address, prefix or ASN; an unknown `include`; any query string on `/open`.
400	`ipv6_not_supported`	An IPv6 address or prefix; on `/me`, a request over IPv6.
401	`unauthorized`	`/v1`: a missing, malformed or unknown key.
402	`credits_exhausted`	`/v1`: the key has no credits left.
404	`not_found`	`/v1`: a reserved or empty path, such as `/v1/` or `/v1/batch`.
405	`method_not_allowed`	Any method but `GET` and `HEAD` (and `OPTIONS` on `/open` and `/me`). The response carries `Allow`.
422	`prefix_too_large`	A prefix shorter than `/16`. See Prefix lookups.
503	`unavailable`	Data or credits momentarily unavailable. Retry.

A path that isn't a route answers 404 with an empty body.

The data feed has its own errors; see Pulls and freshness.