Error Codes
Our API uses standard HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error that failed given the information provided, and codes in the 5xxrange indicate an error with our servers.
HTTP Status Codes
| Code | Description |
|---|---|
| 200 - OK | Everything worked as expected. |
| 400 - Bad Request | The request was unacceptable, often due to a missing or invalid parameter. |
| 401 - Unauthorized | No valid API key provided or the key has expired. |
| 404 - Not Found | The requested BIN was not found in our database. |
| 429 - Too Many Requests | Too many requests hit the API too quickly. Check your plan limits. |
| 500 - Server Error | Something went wrong on our end. Please try again later. |
Common Issues
My 6-digit BIN is not found
If a 6-digit lookup returns a 404, the issuer likely uses an 8-digit BIN. Provide at least 8 digits of the card number for better coverage.
IP Location is missing
The ip_location object only appears if the ip parameter is valid. Ensure your backend is passing the actual cardholder's IP address.
Authentication fails with 401
Verify that you are using the correct X-RapidAPI-Key andX-RapidAPI-Host. Check your subscription status in RapidAPI.
Error JSON Structure
{
"error": "BIN not found",
"meta": {
"request_id": "550e8400-e29b-41d4-a716-446655440003"
}
}