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

# Real-Time Account Updater Error Handling

You will make all Real-Time Account Updater requests to a single endpoint: [/inquiry](/account-updater/endpoint/inquiries). If your request fails for authentication or network errors, you’ll receive an error in the format of the following example:

```json theme={null}
{
  "code": 403,
  "requestId": "8b764b09-5e2d-4562-8a74-6d04fbf574cd",
  "errorDetails": {
    "reason": "unauthorized",
    "message": "Merchant is not authorized to use the resource."
  }
}
```

## API Error Details

| HTTP Response Code | `errorDetails` reason     | `errorDetails` message                                            | Recommended Action                                                                                                             |
| :----------------- | :------------------------ | :---------------------------------------------------------------- | :----------------------------------------------------------------------------------------------------------------------------- |
| 401                | `AuthenticationFailed`    | `The account updater service could not authenticate the request.` | Re-submit your request with correct credentials. Contact your Pagos account manager if the problem persists.                   |
| 403                | `unauthorized`            | `Merchant is not authorized to use the resource.`                 | Re-submit your request with correct `x-merchant-id` in the header. Contact your Pagos account manager if the problem persists. |
| 429                | `concurrentLimitExceeded` | `You exceeded the maximum allowed concurrent API calls.`          | Keep concurrent API calls within the allowed concurrent API request limits.                                                    |
| 500                | `SystemError`             | `A system error occurred.`                                        | Contact your Pagos account manager.                                                                                            |
| 503                | `NetworkError`            | `The network cannot process the request.`                         | Re-submit your request later. Contact your Pagos account manager if the problem persists.                                      |

## Validation Errors

If your request fails due to a validation error (HTTP code 400), the response will include a `code` element that explains the source of the validation error.

The response will be in the format of the following example:

```json theme={null}
{
  error: {
    code: 'account_validation_month_invalid',
    message: "accountsEncrypted property validation's failed.",
    details: {}
  }
}
```

### Validation Error Details

| HTTP Response Code | `error` code                                | Recommended Action                                                 |
| :----------------- | :------------------------------------------ | :----------------------------------------------------------------- |
| 400                | `validation_error`                          | Re-submit your request following guidance in the `details` object. |
| 400                | `account_validation_account_number_invalid` | Re-submit your request with a valid PAN.                           |
| 400                | `account_validation_month_invalid`          | Re-submit your request with a valid PAN expiry month.              |
| 400                | `account_validation_year_invalid`           | Re-submit your request with a valid PAN expiry year.               |

<Tip>
  Pagos is currently working on normalizing the error message response body formats between API Error and Validation Error to aid in integraiton.
</Tip>