The following is a list of HTTP Responses that can be returned from a failed API endpoint invocation.
Error Status Code: 400
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing). [More Information]
- Invalid input data, possible values. - Invalid address. - Invalid public key. - Unsupported token. - Address does not exist. - Address taken. - Invalid request.
Error Status Code: 403
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort. This code is also typically used if the request provided authentication via the WWW-Authenticate header field, but the server did not accept that authentication. [More Information]
- Invalid API access token.
Error Status Code: 429
The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes. [More Information]
- Rate limit has been reached.
Error Status Code: 503
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state. [More Information]
- Temporarily unavailable.
Error Codes by Endpoint¶
Information on the response codes returned from the individual endpoints can be found through the following links:
- Response codes for addresses/addAddress
- Response codes for addresses/getAddressFromPublic
- Response codes for addresses/findLatestTransfers
- Response Codes for transfers/create-signed
- Response Codes for transfers/submit
The following links provide more general information on HTTP Response Codes: