Troubleshooting Charges API error responses

This topic lists all the possible errors you might encounter while using the Charges API and how to resolve them.

Working with errors

This section captures a list of common HTTP errors you might encounter and possible solutions to fix them.

HTTP Error Code	OTA Error Code	Description	Reason and Possible Fix
HTTP 200 Ok	150	Changes are not permitted.	Can occur if the request includes updates to charges that are subject to an override block. If other charge types were updated in the same request that were not subject to an override block, those updates will be applied.
HTTP 400 Bad Request	320	Invalid value.	The API returns `errors.details` and `errors.description` that captures which part of the request body contains invalid values and a description to help you troubleshoot the error. To know more about the exact fields with invalid values, most errors will include values within `errors.details.fields`.
HTTP 400 Bad Request	321	Required field missing.	Use the `errors.details` and `errors.description` field to identify the missing required fields and a description to help you troubleshoot the error. To know more about the exact fields with missing values, parse the `errors.details.fields`.
HTTP 400 Bad Request	394	Invalid item.	Can occur when you specify an unknown parameter in the request. Make sure to specify the right parameters. Check for typos.
HTTP 400 Bad Request	450	Unable to process	Can occur due to one of the following reasons: - Incorrect endpoint URL/HTTP method or invalid JSON body. Make sure to use the correct endpoint URL/HTTP method or check if the request has a valid JSON body.
HTTP 400 Bad Request	497	Authorization error.	The request contains invalid authentication credentials. Provide the correct authentication details.

Overwrite protected response

The following is an example response when a charge is overwrite protected. As a reminder, this response will return 200 HTTP status and any other updates in the request will be applied. For more information, see API validations while managing charges.

{
  "warnings": [
    {
      "message": "Changes are not permitted",
      "code": 150,
      "details": {
        "property_charges": [
          {
            "charge_key": {
              "type": "VAT",
              "guest_origin": "ANY",
              "travel_purpose": "ANY"
            },
            "charge_periods": [
              {
                "applicable": {
                  "from": "2024-11-07"
                }
              }
            ]
          }
        ]
      },
      "description": "The following updates were ignored because the charge was subject to an override block."
    }
  ],
  "errors": [],
  "meta": {
    "ruid": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX"
  }
}

Quick Actions

→ To create and manage charge details, see Managing charge details.