Errors & Limitations

This page provides information about the limitations associated with different subscription plans and how to handle exceptions that may arise during API usage.

Subscription Plans

Each subscription plan has its own set of limitations and features.

To understand the limitations and features associated with each plan, you can refer to our pricing page.

Please note that the actual limitations and features may vary during the beta.

Handling Exceptions

When using the API, you may encounter various exceptions. Each exception has a specific error message and status code associated with it to help you to understand the error.

Here is a list of possible error codes and their meanings:

• 400: Invalid Request Error. The request was invalid or could not be understood by the server.
• 402: Requires Paid Plan Error. The requested operation is limited on the current plan.
• 403: Unauthorized Error. The request requires user authentication.
• 404: Not Found Error. The requested resource could not be found.
• 409: Data Conflict Error. There is a conflict with the current state of the resource.
• 422: Body Error. The request was well-formed but was unable to be followed due to semantic errors.
• 429: Rate Limit Error. The user has sent too many requests in a given amount of time.
• 500: Unexpected Error. An error occurred on the server.

For more detailed information about each exception type, please refer to the exceptions.ts file.

If you have any questions or need further assistance, feel free to reach out to us.