BIN Benchmark API Error Handling - Pagos

If the BIN Benchmark API fails, you’ll receive an error response with an appropriate HTTP status code.

A BIN that doesn’t exist, or that doesn’t have enough transaction volume to calculate a benchmark, is not an error. In both cases, the API returns a 200 response with bin_benchmark set to null; learn more about missing or insufficient network BIN data.There is no BIN_NOT_FOUND error for this endpoint.

Error Responses

HTTP Response Code	Error Code	Description
400	`INVALID_BIN_FORMAT`	BIN is malformed or incorrect length; BIN must contain only numeric digits, be between 6 and 10 characters in length, and can’t include spaces or special characters
400	`MISSING_PARAMETER`	Required `bin` query parameter not provided
401	`MISSING_AUTHORIZATION`	Authorization header not present
401	`INVALID_API_KEY`	API key is invalid or expired
403	`INSUFFICIENT_PERMISSIONS`	Account isn’t opted in to data sharing; the BIN Benchmark API is only available to businesses that have opted in to data sharing with Pagos. Contact your Pagos Account Manager to enable this feature.
429	`RATE_LIMIT_EXCEEDED`	Too many requests made in time window; if you exceed the rate limit of 100 calls every 10 seconds, wait briefly before retrying or consider implementing exponential backoff in your integration.
500	`INTERNAL_ERROR`	Unexpected server error
503	`SERVICE_UNAVAILABLE`	Service temporarily unavailable

Error Response Format

Error responses are returned in the following JSON format:

{
  "message": "INVALID_BIN_FORMAT"
}