The response structure will follow Sabre JSON RPC API Style described in API Style section with the usage of JSON format. See below how to handle errors. 

Error Handling 
 
Application Layer errors, as well as some Transport Layer errors, are returned as part of the response object. The response object schema contains a dedicated optional element for error-related data, and should be provided only when errors occur. 
 
The latter means that every API response will respond with a 200 HTTP status code. For successful responses, content is return as defined in contract. For error responses, only "errors" object will be available. 

Error Format 

The response object contains an optional list of error elements related to both Application and Transport Layers. Each error element contains an error type and error category with an additional description to indicate the cause of the error, and point at the particular field(s) or value(s) in question. 

Error Element 

JSON elements representing a list of errors in a response object will follow Error Format specifications. Here is an example of the response object containing only a list of returned errors: 

{ "errors": [ { "category": "BAD_REQUEST", "type": "REQUIRED_FIELD_MISSING", "description": "must not be null", "fieldName": "toAirportCode", "fieldPath": "ShoppingRequest.oneWay", }, { "category": "BAD_REQUEST", "type": "INVALID_VALUE", "description": "must match \"^[A-Z]{3}$\"", "fieldName": "fromAirportCode", "fieldPath": "ShoppingRequest.oneWay", "fieldValue": "Dallas" } ] } 

Common Error List