Skip to content
InternetData

Errors

Every status code the InternetData API answers, what each means, its body, and what to do about it, for lookups, batches and database downloads.

New to InternetData? Make your first lookup

Lookups

Addresses, ASes and domains answer alike.

StatusMeaningWhat to do
200The answer. A field your plan does not include is absent.Test for presence (Plans and fields).
400Not a valid address, AS number or domain.Check what you sent.
401The key is unknown, revoked or expired.Use a live key, or send none.
403The key lacks the ip.lookup scope, may only be used from addresses this request did not come from, or was sent over plain HTTP.Edit the key in the console; rotate a key sent over HTTP.
429A rate limit, always with Retry-After.Wait that many seconds and retry.
5xxWe could not answer.Retry with backoff.

Batches

POST /batch takes addresses, ASes and domains together. It answers as a lookup does, and also 402 when the key is on the free plan and the batch names more than one item: a batch needs a paid plan. One item that fails comes back in errors with its own status, and the rest still answer.

Database downloads

StatusrcMeaning
302The file: follow Location (curl -L).
400INVALID_FORMAT, INVALID_BUILDThat format or build does not exist.
401No key, an invalid one, one without db.download, or one of no active organization.
403NOT_LICENSED, LICENSE_EXPIREDYour organization holds no license for it, or its term ended; also an address outside the key's allowed ones.
404UNKNOWN_DATASETNo such database.
410BUILD_GONEThat build is older than seven days.
503Today's build is not published yet.

A key sent over plain HTTP is refused everywhere, and should be rotated: it crossed in the clear.

Bodies

Lookups answer an error as {"error": "<message>"}. The database, account and key endpoints answer {"rc": "<CODE>"}, and OAuth answers RFC 6749 errors. Authentication has the account endpoints' codes.