be728e9c01
* feat: Add Mintlify docs * Fixed the mint.json for v2 * Fixed versioning issue * Add titles to ICS feed endpoints * Added errors to v1 * Added rate-limit to API v1 * feat: added v1-v2 differences and v1 auth * Trying to eliminate reasons for v1 not showing on publication * Used the swagger openapi validator * remove deprecated v1 endpoints * Moved api docs into new folders without api-reference * Renamed api to api-reference * removed the versioning * Got rid of anchor warnings * Fixed naming * Just as a test - using the same v2 openapi spec for v1 reference * Removed 'externalDocs' from v1 * Removed securitySchemes * Updated the diff between v1/v2 * Added v1 in front of /attendees to test * Moved paths up and removed externalDocs * Testing - Added content to the response * Reduced paths to 1 * Testing: anything at this point * Fixed validation * Moved the other .mdx files to see if that's disrupting something * Trying with a tab * Empty tags array * Added back servers field * Removed all other schemas * Removed v1 for now * Added platform docs * Language fixes * Added v1 back * add API V1 response for attendees * remove unnecessary endpoint docs in API V1 * Removing platform and API for now * Updated v2 openapi doc --------- Co-authored-by: Syed Ali Shahbaz <alishahbaz7@gmail.com>
58 lines
1.6 KiB
Plaintext
58 lines
1.6 KiB
Plaintext
---
|
|
title: "Errors"
|
|
---
|
|
|
|
Cal.com uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, or something else failed, etc.). Codes in the 5xx range indicate an error with Cal.com's servers (these are rare).
|
|
|
|
<table>
|
|
<thead>
|
|
<tr>
|
|
<th>HTTP</th>
|
|
<th>Status Code</th>
|
|
<th>Summary</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr>
|
|
<td>200</td>
|
|
<td>OK</td>
|
|
<td>Everything worked as expected</td>
|
|
</tr>
|
|
<tr>
|
|
<td>400</td>
|
|
<td>Bad Request</td>
|
|
<td>The request was unacceptable, often due to missing a required parameter</td>
|
|
</tr>
|
|
<tr>
|
|
<td>401</td>
|
|
<td>Unauthorized</td>
|
|
<td>No valid API key provided.</td>
|
|
</tr>
|
|
<tr>
|
|
<td>402</td>
|
|
<td>Request Failed</td>
|
|
<td>The parameters were valid but the request failed.</td>
|
|
</tr>
|
|
<tr>
|
|
<td>403</td>
|
|
<td>Forbidden</td>
|
|
<td>The API key doesn't have permissions to perform the request.</td>
|
|
</tr>
|
|
<tr>
|
|
<td>404</td>
|
|
<td>Not Found</td>
|
|
<td>The requested resource doesn't exist.</td>
|
|
</tr>
|
|
<tr>
|
|
<td>429</td>
|
|
<td>Too Many Requests</td>
|
|
<td>Too many requests hit the API too quickly. We recommend an exponential backoff of your requests.</td>
|
|
</tr>
|
|
<tr>
|
|
<td>500, 502, 503, 504</td>
|
|
<td>erver Errors</td>
|
|
<td>Something went wrong on our servers end. (These are rare.)</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|