Errors Reference
Error Handling Guide
Use this section to debug errors encountered when using Ragie. If you need more help, please reach out to us at [email protected].
Ragie's error response format follows RFC7807. Each error response includes:
- status_code: Same as the HTTP status code
- title: Brief description of the error message
- type: URI that links to this document for further reference
- detail: Human-readable description providing more insight into the error
Note that error responses may include other keys specific to the error.
Example Error Response
{
"detail": "Could not find resource for tenant",
"status_code": 404,
"title": "The specified resource was not found.",
"type": "https://ragie.readme.io/docs/errors#404"
}
Error Codes and Resolutions
Status | Title | Detail |
---|---|---|
400 | Bad request | The request was invalid or cannot be otherwise served. |
401 | Authentication failure | Your request did not provide a valid or well-formatted API key. |
402 | Pages processed exceeded | Exceeded page processing limit. |
402 | Retrievals exceeded | Exceeded retrieval limit. |
403 | Document count limit exceeded | The document limit for your current plan has been exceeded. |
403 | Embedded Connector not enabled | You do not have the connector enabled. It can be enabled in the Ragie application. |
403 | Feature flag disabled | The feature flag has not been enabled for the user |
404 | Resource not found | The specified resource was not found. |
429 | Rate limit exceeded | The rate limit for your current plan has been exceeded. |
500 | Internal server error | An unexpected error occurred on the server. |
400 - Bad Request
The request was invalid or cannot be otherwise served. Ensure that your request is formatted correctly. Find our API reference with examples at https://docs.ragie.ai/reference.
401 - Authentication Failure
Your request did not provide a valid or well-formatted API key.
Resolution:
- Check the provided API key to make sure it is correct and valid. Look for typos and ensure it hasn't expired.
- Reach out to us at [email protected].
402 Pages Processed Exceeded
You've exceeded the page processing limit of your current plan. Paid plans do not enforce a limit.
Resolution:
- Upgrade to a paid plan https://secure.ragie.ai/billing/plans.
- Contact sales to explore the best plan for your use case [email protected]
403 Pages Retrievals Exceeded
You've exceeded the retrieval limit of your current plan. Paid plans do not enforce a limit.
Resolution:
- Upgrade to a paid plan https://secure.ragie.ai/billing/plans.
- Contact sales to explore the best plan for your use case [email protected]
403 - Documents Limit Exceeded
You've exceeded the document limits for your current plan.
Resolution:
- Upgrade your plan to get higher document limits at https://secure.ragie.ai/billing/plans.
- Reach out to us at [email protected].
403 - Feature Flag Disabled
The specified feature flag has not been enabled for the user. Please reach out to Ragie support and tell us what feature you would like us to enable for you.
Resolution:
- Reach out to us at [email protected] with details on the feature you would like enabled.
404 - Resource Not Found
The specified resource was not found. This usually occurs when sending a request to an endpoint that doesn't exist. Make sure the endpoint exists in our API docs: https://docs.ragie.ai/reference, and your request is formatted correctly.
429 - Rate Limit Exceeded
You've exceeded the rate limits for your current plan. We calculate rate limits as requests per minute (e.g. 100 requests/minute). See the rate limits for your tier on the Rate Limits page.
Resolution:
- Upgrade your plan to get higher rate limits at https://secure.ragie.ai/billing/plans
- Stagger your requests to stay within the limits of your plan.
- Reach out to us at [email protected].
500 - Internal Server Error
It's probably our fault. Please reach out to us at [email protected] and tell us what's happening. We'll fix it as soon as possible.
Updated 4 days ago