> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mangopay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HTTP response codes

The Mangopay API uses the following HTTP response codes to indicate the success or failure of a request.

<table>
  <tbody>
    <tr>
      <th class="header">**Response code**</th>
      <th class="header">**Status**</th>
      <th class="header">**Description**</th>
    </tr>

    <tr>
      <td class="table-content">200</td>
      <td class="table-content">OK</td>
      <td class="table-content">Request successful.</td>
    </tr>

    <tr>
      <td class="table-content">204</td>
      <td class="table-content">No content</td>
      <td class="table-content">Request successful with no information returned.</td>
    </tr>

    <tr>
      <td class="table-content">400</td>
      <td class="table-content">Bad request</td>
      <td class="table-content">Request impossible to process due to a logical error (e.g., missing parameter, invalid operation, constraint violation, etc.)</td>
    </tr>

    <tr>
      <td class="table-content">401</td>
      <td class="table-content">Unauthorized</td>
      <td class="table-content">Access to the API resource is not authorized due to an authentication failure (e.g., incorrect client ID, API Key, or URL).</td>
    </tr>

    <tr>
      <td class="table-content">403</td>
      <td class="table-content">Forbidden</td>
      <td class="table-content">Access to the API resource is forbidden, due to an authorization failure (e.g., deactivation of the account or a permission issue regarding a specific feature).</td>
    </tr>

    <tr>
      <td class="table-content">404</td>
      <td class="table-content">Not Found</td>
      <td class="table-content">The requested resource cannot be found.</td>
    </tr>

    <tr>
      <td class="table-content">405</td>
      <td class="table-content">Method Not Allowed</td>
      <td class="table-content">HTTP method is not allowed (e.g., trying a GET instead of a POST).</td>
    </tr>

    <tr>
      <td class="table-content">409</td>
      <td class="table-content">Conflict</td>
      <td class="table-content">The request is not processed due to an identical [idempotency key](/api-reference/overview/idempotency).</td>
    </tr>

    <tr>
      <td class="table-content">411</td>
      <td class="table-content">Length Required</td>
      <td class="table-content">The Content-Length header field is not defined and the server requires it.</td>
    </tr>

    <tr>
      <td class="table-content">413</td>
      <td class="table-content">Payload Too Large</td>
      <td class="table-content">The request entity is larger than the server is able to process (e.g., KYC document file larger than 10MB).</td>
    </tr>

    <tr>
      <td class="table-content">415</td>
      <td class="table-content">Unsupported Media Type</td>
      <td class="table-content">The format of the media sent is not supported by the server (e.g., wrong file format for KYC document file).</td>
    </tr>

    <tr>
      <td class="table-content">422</td>
      <td class="table-content">Unprocessable Entity</td>
      <td class="table-content">The request cannot be fulfilled due to semantic errors.</td>
    </tr>

    <tr>
      <td class="table-content">429</td>
      <td class="table-content">Too Many Requests</td>
      <td class="table-content">Too many requests have been sent in a given period of time ([rate limiting](/api-reference/overview/rate-limiting)).</td>
    </tr>

    <tr>
      <td class="table-content">500</td>
      <td class="table-content">Internal Server Error</td>
      <td class="table-content">The server encountered an issue.</td>
    </tr>
  </tbody>
</table>