Skip to main content

Understanding Request Errors with the Corti API

Updated over a week ago

When working with the Corti API, it's important to know how to handle error responses if something doesn’t go as expected. Below is an overview to help you understand common error types, why they happen, and how to avoid them.

Common request errors

  • Bad request or invalid ID (400)

  • Unsupported language (400)

  • Invalid token or access forbidden (403)

  • Interaction, document, recording, or transcript not found (404)

  • Trial period expired (429)

Important Things to Include in Your Requests

To avoid these errors, make sure your requests always include:

  • A valid Bearer token for authentication

  • The correct tenant-name to specify your environment

  • Proper configuration values and json format for your intended use

  • Timely setup when using WebSocket connections


Have a question for our team?

Click Support in the bottom-left corner of the console to submit a ticket or reach out via email at [email protected] and we'll be happy to assist you.

Additional resources:

🔗 Visit our error documentation for a deeper dive into API error responses

Did this answer your question?