Errors
Diagnose failed requests and handle errors returned by the Lithic API.
Use this information to diagnose failed requests and fine-tune your exception handling.
400 Bad request
| Message | Description |
|---|---|
| [query] is not a valid parameter | A parameter in the query given in the request does not match the valid queries for the endpoint |
401 Unauthorized
| Message | Description |
|---|---|
| User has not been authenticated | Invalid or missing API key |
| API key is not active | The API key used is no longer active |
| Could not find API key | The API key provided is not associated with any user |
| Please provide API key in Authorization header | The Authorization header is not in the request |
Please provide API key in the form Authorization: [api-key] | The Authorization header is not formatted properly |
| Insufficient Privileges. Issuing API key required | Write access requires an Issuing API key. Contact support.lithic.com |
| Insufficient privileges to create virtual cards. | Creating virtual cards requires an additional privilege. Contact support.lithic.com |
422 Unprocessable entity
| Message | Description |
|---|---|
| Authorization failed (in simulation) | An authorization fails when simulating an authorization |
429 Too many requests
| Message | Description |
|---|---|
| Rate limited, too many requests per second | User has exceeded their per second rate limit |
See Rate limits for limits per resource and retry guidance.
5xx Server errors
Lithic APIs may return HTTP 5xx errors in case of issues on Lithic's side. This always indicates a server-side error, and the specific HTTP error should not matter to the caller. The recommended action is to retry the request. If the issue persists, check our Status Page and contact support.lithic.com.
| Code | Name | Description |
|---|---|---|
| 500 | Internal Server Error | There was a processing error on the server-side. |
| 502 | Bad Gateway | There was a processing error on the server-side due to network configuration |
| 503 | Service Unavailable | There was a processing error on the server-side due to unavailability of an internal service |
| 504 | Gateway Timeout | There was a processing error on the server-side due to network timeout |
Updated 3 days ago
Did this page help you?
