Skip to content

1.5 - Sample Query and Output

The result is JSON, in the legacy feed's envelope: StatusCode (the HTTP status), Status (ESUCC on success, EFAIL on an error), Message, Debug (always null) and Result, the operation's data. XML, HTML and text output are not served, and a format parameter is accepted and ignored. Sample queries and their output are in 1.2 and 1.3.

200 Success of the request

The kind of error says where it comes from. A missing, unknown, revoked or expired API key, or a request that sends only the old AppKey header, is answered 401. A key whose permissions or plan do not include the operation, a suspended account, or a request from an address or origin the account does not allow is answered 403. A key that has used up its rate limit per minute or its monthly quota is answered 429. These refusals are a JSON object {"status": "error", "message": "..."} whose message says what is wrong. Every other error is in the envelope, with Status EFAIL, the reason in Message and Result null.


In general, the basic rules for HTTP response codes are as follows:

404 No operation at this path, or no data for the identifiers requested
500 Is a server error
429 Too many requests: the key's rate limit per minute or its monthly quota is used up


Attention: only an InfoTrie API key, sent in the X-API-Key header, opens the API. Keys of the old AppKey header were not carried over: ask InfoTrie for a new key.