Errors

The iPint API uses standard HTTP status codes to indicate success or failure.

HTTP status codes

Code	Meaning
`200`	Success
`400`	Bad request — invalid parameters
`401`	Unauthorized — invalid or missing API key / signature
`404`	Not found — resource doesn't exist
`429`	Too many requests — rate limit exceeded
`500`	Server error — try again later

Error responses are JSON objects:

{
  "error": "Invalid invoice_id",
  "code": "INVALID_INVOICE_ID",
  "message": "The provided invoice_id does not exist or has expired."
}

Field	Type	Description
`error`	string	Short error description
`code`	string	Machine-readable error code
`message`	string	Detailed human-readable message

Code	Cause	Fix
`INVALID_API_KEY`	Missing or incorrect API key	Check your API key in the `X-API-Key` header
`INVALID_SIGNATURE`	HMAC signature mismatch	Ensure you're signing with the correct API secret
`INVALID_INVOICE_ID`	Invoice doesn't exist or expired	Verify the invoice ID from the `/checkout` response
`AMOUNT_OUT_OF_RANGE`	Amount below minimum or above maximum	Check limits via `GET /prices`
`UNSUPPORTED_CRYPTO_CODE`	Asset not supported	Check `GET /currencies` for valid codes

If you exceed the rate limit, you'll receive a 429 response. Implement exponential backoff and retry logic in your integration.

Need higher rate limits for production? Contact help@ipint.io.