Errors

The Monierate API will return JSON error messages if an issue arises, helping you debug your applications and manage alerts.

All Monierate API errors follow a standard format.

Here’s an example, produced when an invalid api_key is provided:

{
    "status": "error",
    "message": "invalid_api_key",
    "description": "Invalid API key"
}

Here are some of the most common errors you may encounter:

Message	Status Code	Details
"not_found"	404	Client requested a non-existent resource/route
"missing_api_key"	401	Client did not provide an API Key
"invalid_api_key"	401	Client provided an invalid API Key
"not_allowed"	429	Client doesn't have permission to access the requested route/feature
"access_restricted"	403	Access restricted due to repeated over-use (status: 429) or other reasons
"invalid_base"	400	Client requested rates for an unsupported base currency

If you encounter an error not listed here or have any other issues, please don't hesitate to contact us.