---
updatedAt: 2026-09-16T15:22:54.000Z
agentTools:
  projectIndex: https://developer.launchpay.com/llms.txt
---

# API Status Codes

Every response from the New Accounts API includes an HTTP status code: a short number that summarizes how the request went.

<Cards columns="3">
  <Card title="2xx — Success" icon="fa-circle-check" iconColor="#2ca7b5">
    The request was accepted. Check the body to confirm the work finished.
  </Card>

  <Card title="4xx — Your request" icon="fa-triangle-exclamation" iconColor="#f9a229">
    Something in the request needs to change before it will succeed.
  </Card>

  <Card title="5xx — Our side" icon="fa-server" iconColor="#dc2529">
    Something went wrong while we processed a request that may have been valid.
  </Card>
</Cards>

## Quick reference

<Table>
  <thead>
    <tr>
      <th>
        Code
      </th>

      <th>
        Meaning
      </th>

      <th>
        Typical cause & what to do
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        `200 OK`
      </td>

      <td>
        Request succeeded
      </td>

      <td>
        The call worked and any data is in the body.

        On merchant application submit endpoints a `200` can still report a validation problem, so check the response body before treating it as done.
      </td>
    </tr>

    <tr>
      <td>
        `202 Accepted`
      </td>

      <td>
        Accepted for background processing
      </td>

      <td>
        Your request was valid and queued (uploads, notes, and asynchronous submissions). Accepted, not yet complete.
      </td>
    </tr>

    <tr>
      <td>
        `400 Bad Request`
      </td>

      <td>
        The request was invalid
      </td>

      <td>
        Something in the request was wrong, and the response names the fields that failed. Usually a value is in the wrong format, such as text where a number belongs or a misspelled status. Read the body message, fix the input or credentials, and resend.
      </td>
    </tr>

    <tr>
      <td>
        `401 Unauthorized`
      </td>

      <td>
        Authentication failed or was missing
      </td>

      <td>
        Missing or invalid credentials. Check your API key. See [New Accounts API Authentication](https://developer.launchpay.com/docs/new-accounts-authentication).
      </td>
    </tr>

    <tr>
      <td>
        `403 Forbidden`
      </td>

      <td>
        Not permitted, or credentials rejected
      </td>

      <td>
        Two situations produce this code, and the response body tells you which.<br /><br />1. Plain text reading Forbidden: Your credentials do not grant access to this endpoint. means the endpoint is not part of the Launchpay API offering. Confirm that the endpoint is listed within the New Accounts API Reference.<br /><br />2. An empty body means the request was to the Digital Signature endpoint, which returns 403 when the credential is missing, invalid, or issued for a cobrand other than the one in the URL.
      </td>
    </tr>

    <tr>
      <td>
        `404 Not Found`
      </td>

      <td>
        Route, tenant, or resource does not exist
      </td>

      <td>
        The URL path is wrong. Verify the path.
      </td>
    </tr>

    <tr>
      <td>
        `500 Internal Server Error`
      </td>

      <td>
        An unexpected error on our side
      </td>

      <td>
        Something failed while processing your request, which may have been valid. Retry and contact us on the <Anchor target="_blank" href="https://infinicept.atlassian.net/servicedesk/customer/portal/13">Customer Support Portal</Anchor> if it persists.
      </td>
    </tr>
  </tbody>
</Table>

<br />

# Support

> Have a question? Contact us on the <Anchor target="_blank" href="https://infinicept.atlassian.net/servicedesk/customer/portal/13">Customer Support Portal</Anchor>.
>
> Learn about updates in our [Changelog](https://developer.launchpay.com/changelog).

<br />

<br />