Loading page…
Raspberry API uses conventional HTTP status codes. A 2xx means success; any other status carries a JSON error message explaining what to fix.
| Status | Meaning | How to fix |
|---|---|---|
| 200 OK | The request succeeded and the JSON body holds your data. | — |
| 400 Bad Request | A required parameter is missing or malformed — e.g. no ticker, an unknown market id, or a bad date. | Check the endpoint's parameters and value formats. |
| 401 Unauthorized | No API key was sent, or the key isn't recognized. | Send a valid ra_live_ key in the x-api-key header. |
| 403 Forbidden | The key is valid but your plan doesn't include this product, or the account has been disabled. | Use a key scoped to this API, or contact support if the account is disabled. |
| 404 Not Found | The resource doesn't exist — an unknown strategy id, or a ticker with no data on file. | Verify the id/symbol in the path or query. |
| 429 Too Many Requests | You've reached your monthly request limit for the current period. | Wait for the monthly reset or upgrade your plan. |
| 500 Server Error | Something failed on our side, or an upstream data source was briefly unavailable. | Retry after a short delay; if it persists, contact support. |
Every non-2xx response is JSON with a single error string:
{
"error": "Missing API key. Pass it as header 'x-api-key'."
}Seeing 429? Check your plan's monthly cap and how counting works.