API errors follow the RFC 7807 Problem Details format:
{
"type": "https://rateflowapi.com/errors/invalid-api-key",
"title": "Invalid API Key",
"status": 401,
"detail": "The API key provided is missing or invalid."
}
| Field | Description |
|---|---|
type |
A URI that identifies the error type |
title |
A short human-readable summary |
status |
The HTTP status code |
detail |
A detailed explanation of the error |
| Error Type | HTTP Status | Description |
|---|---|---|
invalid-api-key |
401 | API key is missing or invalid |
inactive-account |
403 | Account is blocked, API key is deactivated, or email is not verified |
plan-upgrade-required |
403 | The requested feature is not available on your current plan (e.g. historical data on a Free plan) |
unsupported-currency |
422 | The currency code is not recognized |
invalid-date |
422 | The date format is invalid or the date is in the future |
invalid-amount |
422 | The amount is not numeric or outside the valid range (0 – 1,000,000,000,000) |
no-data-available |
404 | No exchange rate data is available for the requested date or currency pair |
quota-exceeded |
429 | Monthly rate limit has been reached. Includes a Retry-After header |
service-unavailable |
503 | Rate limiting service is temporarily unavailable |
{info} When you receive a
429error, check theRetry-Afterheader for the number of seconds to wait before retrying. See Rate Limits for details.