Errors
Code to common errors to prevent a traveler's workflow from being interrupted.
REST APIs
REST APIs: Verify your token credentials were set-up correctly.
# | HTTP Status Code | Message | Text | Resolution |
---|---|---|---|---|
1 | 400 | Bad Request | Invalid format for request |
1. Verify that your request includes valid parameters or values. 2. Verify that the grant_type in the request payload. |
2 | 400 | ERR.2SG.CLIENT.INVALID_REQUEST | Verify that your request includes valid parameters or values. Check API documentation. | |
3 | 401 | Unauthorized | Not authorized to make this request. Check access level and refer to API documentation for access information. | Verify your token credentials. |
4 | 401 | Unauthorized | invalid_client | Verify your token credentials. |
5 | 401 | Unauthorized | Credentials are missing or the syntax is not correct | Verify that your base64-encoded token credentials were constructed properly. |
6 | 401 | Unauthorized | Wrong clientID or clientSecret | Verify password for the client ID. |
7 | 401 | Unauthorized | ERR.2SG.SEC.MISSING_CREDENTIALS | Verify you are using the correct data type. |
8 | 401 | Unauthorized | ERR.2SG.SEC.INVALID_CREDENTIALS | Verify your token credentials. |
9 | 403 | Forbidden | Request is for a resource that is forbidden |
1. Verify that your token credentials allow authorization to call this API. 2. Contact your Sabre account manager to verify access. |
10 | 403 | ERR.2SG.SEC.NOT_AUTHORIZED |
1. Verify that your token credentials allow authorization to call this API. 2. Contact your Sabre account manager to verify access. |
|
11 | 403 | ERR.2SG.CLIENT.SERVICE_UNKNOWN |
1. Verify URL is valid. 2. Verify whether your request has required segments, such as a version number. Check API documentation. |
|
12 | 404 | Not Found | Response does not contain any data |
1. No data found to fulfill the request. You might consider using fewer parameters/filters. 2. URL has missing segments, such as a version number. Check API documentation. 3. Verify URL is valid. Check API documentation. |
13 | 405 | Method Not Allowed | Method is not valid or authorized for this endpoint. Check API documentation. | |
14 | 406 | Not Acceptable | Requested resource is only capable of generating content not acceptable according to the Accept headers sent in the request. | |
15 | 413 | ERR.2SG.CLIENT.INVALID_REQUEST |
1. Request URL too long. 2. Reduce the number of request parameters in the URL. Separate parameters into multiple requests. |
|
16 | 413 | FULL head |
1. Request URL too long. 2. Reduce the number of request parameters in the URL. Separate parameters into multiple requests. |
|
17 | 429 | too many requests | temporarily_unavailable |
1. Internal limit has been exceeded. 2. Wait at least 500 milliseconds and resend the request. |
18 | 429 | Throttled | Active token count is exceeded |
1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API. 2. Wait at least 500 milliseconds and resend the request. |
19 | 429 | ERR.2SG.GATEWAY.REQUEST_THROTTLED |
1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API. 2. Wait at least 500 milliseconds and resend the request. |
|
20 | 500 | Server Error |
1. API encountered an unexpected condition that prevented it from fulfilling the client's request. 2. Wait at least 500 milliseconds and resend the request. |
|
21 | 500 | ERR.2SG.SEC.INTERNAL_PROCESSING_ERROR |
1. API encountered an unexpected condition that prevented it from fulfilling the client's request. 2. Wait at least 500 milliseconds and resend the request. |
|
22 | 500 | ERR.2SG.GATEWAY.TIMEOUT | Wait at least 500 milliseconds and resend the request. | |
23 | 500 | ERR.2SG.GATEWAY.INTERNAL_PROCESSING_ERROR | Wait at least 500 milliseconds and resend the request. | |
24 | 500 | ERR.2SG.GATEWAY.INVALID_PROVIDER_RESPONSE |
1. The server cannot understand the response of the service because of bad format or failure to comply with protocol. Contact the Sabre support desk. 2. Wait at least 500 milliseconds and resend the request. |
|
25 | 500 | ERR.2SG.GATEWAY.PROVIDER_CONNECTION_ERROR |
1. Your request encountered a transport error. 2. Wait at least 500 milliseconds and resend the request. |
|
26 | 500 | Connection error | ERR.2SG.PROVIDER_CONNECTION_ERROR |
1. Your request encountered a transport error. 2. Wait at least 500 milliseconds and resend the request. |
27 | 503 | Service Unavailable | Server is currently unavailable. Please try again later and report if the problem persists. | Wait at least 500 milliseconds and resend the request. |
28 | 504 | Gateway Timeout | Server timed out trying to fulfill the request. Please try again later and report if the problem persists. | Wait at least 500 milliseconds and resend the request. |
SOAP APIs
SOAP APIs: Verify your token credentials were set-up correctly.
# | Text | Resolution |
---|---|---|
1 | USG_AUTHENTICATION_FAILED | Verify that your token credentials were set-up properly. Verify your session token is valid.
|
2 | USG_AUTHENTICATION_NOT_ALLOWED | Verify your token credentials are as a binary security token rather than passing the user credentials in the request.
|
3 | USG_INVALID_SECURITY_TOKEN | Verify your token credentials.
|
4 | USG_PASSWORD_NOTFOUND | Verify the password for your token credentials.
|
5 | USG_PASSWORD_CHANGE_REQUIRED | Reset your password using the CREATE agent.
|
6 | USG_AUTHORIZATION_FAILED | Verify that your token credentials allow you to call this API. Contact your Sabre account manager to verify access.
|
7 | USG_CONNECTOR_IS_BUSY |
1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API. 2. Wait at least 500 milliseconds and resend the request. |
8 | USG_IS_BUSY |
1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API. 2. Wait at least 500 milliseconds and resend the request. |
9 |
USG_SECURITY_ICE_ERROR |
1. An internal error prevented the request from being processed. 2. Wait at least 500 milliseconds and resend the request. 3. Contact Sabre Support if the error persists. |
10 | USG_INVALID_SESSION | Do not attempt simultaneous usage of the same session token/session. Get a new token.
|
11 | USG_RESOURCE_UNAVAILABLE |
1. You have exceeded the maximum number of sessions. 2. Terminate unused active session tokens, wait at least 500 milliseconds and resend the request. |
12 | USG_RESOURCE_BLOCKED |
1. Session creation blocked for the given user. 2. Contact Sabre. |
13 | USG_SERVICE_IS_BUSY |
1. Maximum number of concurrent requests for the API has been exceeded. Contact your Sabre account manager to determine or increase your allocated concurrent request limit for this API. 2. Wait at least 500 milliseconds and resend the request. |
14 |
USG_SERVICE_PROVIDER_ERROR | Wait at least 500 milliseconds and resend the request.
|
15 | USG_NO_RESPONSE_FROM_JMSRECEIVER_IN_TIME | Wait at least 500 milliseconds and resend the request.
|
16 | SC_SERVICE_UNAVAILABLE | Wait at least 500 milliseconds and resend the request.
|
17 | USG_COULD_NOT_COMPLETE_REQUEST |
1. Your application may be experiencing an internal security error. 2. Wait at least 500 milliseconds and resend the request. |
18 | USG_IIOP_OBJECT_NOT_EXIST |
1. Your application may be experiencing an internal security error. 2. Wait at least 500 milliseconds and resend the request. |
19 |
USG_IIOP_TRANSIENT_EXCEPTION |
1. Your application may be experiencing an internal security error. 2. Wait at least 500 milliseconds and resend the request. |
20 |
USG_CONVERSATION_ID_REQUIRED | Verify that eb:ConversationId element is in the SOAP header.
|
21 | USG_INVALID_ACTION | Verify the format of your SOAP envelope.
|
22 | USG_INVALID_EBXML | Verify required ebXML element or attribute is valid.
|
23 | INVALID_VERSION |
1. Verify the version number for the specified service action code. 2. Check documentation for the API to ensure you are specifying the correct version. |
24 |
MISSING_VERSION |
1. Include a valid version number. 2. Check documentation for the API to ensure you are specifying the correct version. |
25 | USG_SERVICE_VERSION_DEPRECATED |
1. The version number for the specified service and given user is deprecated. 2. Contact your Sabre account manager. |
26 | USG_MOM_SERVICE_PROVIDER_INFRASTRUCTURE_ERROR |
1. An internal error prevented the request to be processed. 2. Wait at least 500 milliseconds and resend the request. 3. Contact Sabre support if the error persists. |
27 | USG_CLIENT_ID_NOT_SUPPORTED | Do not send ClientId credentials in a sessionless service invocation. They can be passed only in SessionCreateRQ / TokenCreateRQ requests. |
28 | USG_CLIENT_ID_NOT_FOUND |
1.ClientId is required in SessionCreateRQ version 2.0.0. 2. Verify that it is present in the SOAP security header. |
29 | USG_CLIENT_SECRET_NOT_FOUND |
1. ClientSecret is required in SessionCreateRQ version 2.0.0. 2. Verify that it is present in the SOAP security header. |
30 | USG_CLIENT_AUTHENTICATION_ERROR |
1. Indicates that clientId and clientSecret validation failed on ESSM side. 2. Verify their correctness. |
API Specific Errors
Bargain Finder Max
# | Error | Cause | Resolution |
---|---|---|---|
1 | No Availability |
Either your PCC is not enabled to consume BFM or the tier level (50, 100, 200) you specified does not match your BFM agreement. |
1. Ensure your PCC is enabled to consume BFM. Contact your Sabre account manager to validate if your PCC has been configured to consume BFM. 2. Adjust the BFM tier level to the appropriate one according to your BFM agreement. |
2 |
NO FLIGHT SCHEDULES FOR QUALIFIERS USED |
No flights results could be found with the qualifiers used in your request. |
Review the qualifiers used on your request to ensure those are not overly-restrictive – Example, requesting non-stop flights in a route where non-stop flight do not operate.
|
3 |
Communication error code=104: Connection reset by peer |
Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
4 |
Communication error: Transmission timeout |
Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
5 | DSF server returned an error: Insufficient resources to process the request | Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
6 |
MAX NBR COMBINATIONS EXCEEDED |
Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
Enhanced Seat Map
# | Code | Error | Cause | Resolution |
---|---|---|---|---|
1 | 14 | Airline code and/or flight number invalid | Airline code and/or flight number invalid. | Validate the values entered in the request. |
2 | 32 | PRS NOT ALLOWED THIS INVENTORY | Selected RBD (class of service) does not allow seat selection prior to check-in (PRS - Pre-reserved seat) for the selected route. As an example, most "Basic Economy" fares do not allow seat selection prior to check-in. | Validate the specific airline rules associated with the selected class of service. |
3 | 102 / 308 | UNABLE TO DISPLAY |
1. One or more values were not entered correctly in the request.. Eg. flight number does not correspond to marketing airline or class of service (RBD) does not exist for requested flight. 2. Seat selection is not yet available (eg. airline only allows seat display/selection 3 months prior to departure). |
1. Validate the values entered in the request. 2. Validate advance seat selection rules for the specific airline. |
4 | 111 | INVALID FLIGHT DATE | Flight does not operate in the requested date or request is for a past date. | Validate the values entered in the request. |
5 | 112 | INVALID FLIGHT NUMBER | Flight number is not valid for the requested airline. | Validate the values entered in the request. |
6 | 134 |
PRS NOT ALLOWED THIS CLASS OR ZONE |
Selected RBD (class of service) does not allow seat selection prior to check-in (PRS - Pre-reserved seat) for the selected route. | Validate the specific airline rules associated with the selected class of service. |
7 | 135 |
FLIGHT OPERATED BY ANOTHER CARRIER |
The specified flight is a code share flight where the operating airline does not cascade seat map information to the marketing carrier. | No corrective action, seat map cannot be displayed. |
8 | 180 | Terminal identification invalid - POS.PCC does not match client credentials | You do not have viewership access over the PCC defined in POS. |
1. Validate the values entered in the POS field. 2. Verify the viewership level you have over the POS PCC. |
9 | 312 | Required data missing: airline flight number | Flight number is required in the request. | Validate the elements entered in the request. |
10 | 326 | UNDER AIRPORT CONTROL |
You attempted to display the seat map but the airline has restricted access to only allow seat modification to the airline's airport personnel. Time frame may vary from 24hrs to 72hrs depending on the airline's internal process. |
1. No corrective action, seat map cannot be displayed. 2. If timeframe before departure is longer than 72hrs, please contact Sabre support for assistance. |
11 | 450 | Unable to retrieve the requested seatmap |
1. Selected RBD (class of service) does not exist for requested flight. 2. Selected RBD (class of service) does not allow seat selection prior to check-in. 3. The specified flight is a code share flight where the operating airline does not cascade seat map information to the marketing carrier. |
1. Validate the values entered in the request. 2. Validate airline restrictions associated with the specific RBD (class of service). 3. No corrective action, seat map cannot be displayed. |
12 | 700001 | Internal service error |
1. One or more values were not entered correctly. Eg. <DepartureDate> contains an invalid date or has been added in an invalid format. 2. Internal processing error. |
1. Validate the values (and value formats) entered in the request. 2. Contact Sabre support if the error persists. |
13 | 700101 | Incomplete request - FareAvailQualifiers.TravellerID is required | TravellerID is required in the request when specifying frequent flyer information. | Validate the elements entered in the request. |
14 | 700101 | Incomplete request - GivenName and surname are both required | GivenName & Surname are required in the request when specifying frequent flyer information. | Validate the elements entered in the request. |
15 | 700101 | Incomplete request - POS element is required | POS element is required in the request. | Validate the elements entered in the request. |
16 | 700105 | XML marshall/unmarshall error occurred | One or more values were not entered correctly. | Validate the values entered in the request. |
17 | 700201 | Invalid PRS response |
1. One or more values were not entered correctly. 2. The marketing airline does not participate in interactive seat maps. |
1. Validate the values entered in the request. 2. No corrective action, the seat map cannot be displayed. |
18 | 700202 | Timeout exception occurred - PRS |
This happens when attempting to connect to the airlines' Pre Reserved seat inventory and the request is taking too long (and times-out). This occurs sporadically in Sabre's certification (CERT) environment. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
End Transaction
# | Error | Cause | Resolution |
---|---|---|---|
1 | *PAC TO VERIFY CORRECT NBR OF ACCTG LINES - THEN ET TO CONTINUE |
The number of passengers in the PNR you are trying to commit does not match the number of accounting lines. It's a common message after you have exchanged a ticket. |
1. This is a soft error (warning) which can be bypassed by sending another End Transaction API call (Passenger Details can be used as well). Please ensure that you do not specify the <Source/> element as part of your subsequent request as enabling it will get your application stuck in a loop as the same warning message will reappear. 2. Please consider using either Passenger Details or Create Passenger Name Record (SOAP | REST) APIs in your workflow as these soft errors are handled automatically by these services. |
2 | DIRECT CONNECT MESSAGES RECEIVED - ENTER *A OR *IM |
The airline you have booked sent a direct connect message back to the PNR. This is common when selling airlines such as Frontier or Delta. |
1. This is a soft error (warning) which can be bypassed by sending a Send Sabre Command API call with <HostCommand>*IM</HostCommand>. After you have sent this message you will need to send another End Transaction API call (Passenger Details can be used as well). 2. Please consider using either Passenger Details or Create Passenger Name Record (SOAP | REST) APIs in your workflow as these soft errors are handled automatically by these services. |
3 |
INFANT DETAILS REQUIRED IN SSR - ENTER 3INFT/... |
There's an infant in the reservation but there's no SSR (Special Service Request) element informing the airline the required infant details. Airlines require additional details such as the infant's date of birth (to validate that the infant's age is < 2 years). |
1. Call the Passenger Details API in order to add the required SSR and end the PNR. 2. If already using the Passenger Details or Create Passenger Name Record (SOAP | REST) API to build a PNR, you need to add the element in the payload request. Note: Not very familiar with Sabre reservations? Check this. |
4 |
PQ REQUIRED BEFORE END TRANSACTION |
The PCC where you are creating a reservation has a configuration requiring that a Price Quote (PQ) record needs to be created in the PNR before allowing End Transaction. |
1. PQ creation can be configured within the Orchestrated Air Booking (or Create Passenger Name Record (SOAP | REST)) API. Enabling the <PriceRequestInformation Retain="true"> in the request will store the fare (PQ) in the PNR. 2. If your business workflow does not require fares to be stored in the PNR, you may want to consider contacting representatives from your organization with access to perform PCC/TJR updates to disable this requirement. 3. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team to get assistance on how to disable the "PQ required" configuration. Note: Not very familiar with Sabre reservations? Check this. |
5 | NEED TICKETING/TIMELIMIT - USE 7 OR 8 | Ticketing time limit is missing in the reservation, and this a mandatory element. |
1. Call the Passenger Details API in order to add the ticketing time limit and end the PNR (<Ticketing TicketType="7T-A"/>). 2. If already using the Passenger Details or Create Passenger Name Record (SOAP | REST) API to build a PNR, you need to add the element in the payload request. Note: Not very familiar with Sabre reservations? Check this. |
7 | .PASSENGER TYPE FUNCTION INACTIVE IN TJR |
This response occurs when you attempt to store a passenger type code in the PNR and you do not have the "Store Passenger Type In PNR" active in your PCC/TJR. Most likely you are performing a transaction in brand new PCC where this setting has not been enabled. |
1. If representatives from your organization have access to perform PCC/TJR updates, contact them to perform a W/PT‡ON activation on the used PCC. 2. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team. |
8 | TICKET/TIMELIMIT MUST PRECEDE TRAVEL DATE-UPDATE TICKET FIELD | The ticket time limit element used in the PNR needs reflects a date beyond the date of the first departure flight in the itinerary. |
1. Ensure your <Ticketing TicketType/> date is configured for a date prior to the first departure flight. 2. Consider using <Ticketing TicketType="7T-A"/> if you don't need to specify a concrete date. |
/offers/price API
# | Code | Error | Cause | Resolution |
---|---|---|---|---|
1 | 400 | Invalid request header or body format | Invalid request header or body format. | Validate the values entered in the request. |
2 | 403 | Invalid authentication header | The authentication token used in the request is not supported. | Validate that the authentication token used in the request is valid (only ATK session-less token are supported by this API). |
3 | 404 | Failed to retrieve response from external service | The offer Id used in the request has expired or doesn't exist. | Generate a new offer and retry your request. |
4 | 404 |
Bad Gateway Failed to retrieve response from external service |
Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
5 | 504 | Timeout external service | Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
/orders/create API
# | Code | Error | Cause | Resolution |
---|---|---|---|---|
1 | 500 | Security token error: Resource is not found | The set of credentials (EPR) used to create the Order is configured to consume internal sessions from a TAM Profile other than it's own PCC -and the EPR doesn't contain the necessary security to do so-. | Validate that this is the actual desired provisioning setting (consume sessions from a different PCC); if it is, validate if the EPR contains the SUBACC keyword (required to consume sessions from a PCC different from it's own). |
2 | 020001 | No offer available: Offer not found: XXXXXXXXXXXXXXXXXX | The offer Id used in the request has expired. | Generate a new offer and retry your request. |
3 | 050002 / 050007 |
Error while invoking external client: [I/O error: Read timed out; nested exception is java.net.SocketTimeoutException: Read timed out] | Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
4 | 050002 / 050007 |
External service returned error in orderViewRS (code: [325] message: [Error in XX's response.]). | Temporary processing error (XX is the supplier's code). |
1. Retry your request. 2. Contact Sabre support if the error persists. |
5 | 050002 / 050007 |
External service returned error in orderViewRS (code: [325] message: [Invalid or expired Offer XXXXXXXXXXX-XXX-XXXX-XXXX-X]). | The offer Id used in the request has expired. | Generate a new offer and retry your request. |
6 | 050005 | Response message fault: [Message OrderCreateRQ not implemented for _null_] | The selected offer is not NDC sourced, the current release of this Offers/Orders solution does not support the creation of an Order that is not NDC sourced. |
1. Validate the source of selected offer, if it is ATPCO or LCC you need to select a different one (NDC sourced) and try again. 2. As per the current release, in order to book an ATPCO or LCC offer you need to do so by using the traditional API stack (eg.Create Passenger Name Record SOAP | REST) API). 3. If you have selected an NDC sourced offer, retry your request and contact Sabre support if the error persists. |
7 | 060016 | External service call exception: [Profile not found.] | This error is returned when the data in the offer contains a codeshare flight. At least one flight segment in the selected offer that has a carrier code not listed on the NDC Airline Profile table, hence the message “Profile not found”. | Select a different offer and retry your request. |
8 | 500700 | ET PROCESSING ERROR NEED ADDRESS - USE W- | The PCC used to create the Order requires the agency's address to be present in the reservation (TJR setting). The first release of the Sabre /orders/create API does not support the agency's address field in the request. |
1. If representatives from your organization have access to perform PCC/TJR updates, contact them to discuss this change (W/KPAD‡OFF). 2. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team. 3. Alternatively you can use a different PCC where this setting is not mandatory. |
9 | 500700 | ET PROCESSING ERROR NEED 5/ | The PCC used to create the Order requires the client's address to be present in the reservation (TJR setting). The first release of the Sabre /orders/create API does not support the client's address field in the request. |
1. If representatives from your organization have access to perform PCC/TJR updates, contact them to discuss this change (W/KRAD‡OFF). 2. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team. 3. Alternatively you can use a different PCC where this setting is not mandatory. |
10 | 500700 | ET PROCESSING ERROR NEED * IN NAME FIELD | The PCC used to create the Order requires an * followed by at least one letter or number on the passenger's name field to be present in the reservation (TJR setting). The first release of the Sabre /orders/create API does not support this field in the request. |
1. If representatives from your organization have access to perform PCC/TJR updates, contact them to discuss this change (W/KAST‡OFF). 2. If your organization does not have access to perform PCC/TJR updates, contact your Sabre account team. 3. Alternatively you can use a different PCC where this setting is not mandatory. |
/orders/change API
# | Code | Error | Cause | Resolution |
---|---|---|---|---|
1 | 060132 | Provided external order id [XXXXXXXXXX] not found in order. | The External Order id specified in the request is not valid. |
1. Validate your request parameters and try again. 2. If you are performing a fulfillment request, the External Order id element is no longer required and should be omitted from the request. |
2 | 060119 | Unknown error | Invalid or expired order Id. | Validate the value entered in the "id" field is a valid Sabre order Id. |
3 | 100002 | There was an error while mapping the response from OrderFulfillmentService | Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
4 | 100003 | Fulfillment error response: Null ORDER ID | The Sabre order Id you attempted to modify (eg. fulfill) has been canceled and no longer has an order Id on the supplier side. | Validate the status of your Sabre order Id (it needs to contain at least one valid supplier order Id). |
5 | 100003 | Fulfillment error response: OrderItem XXXXXXXXXXX-XXXX-XXXX-XXX-X-X referenced not found in Order | The Sabre order Id you attempted to modify (eg. fulfill) has been canceled and no longer has an order Id on the supplier side. | Validate the status of your Sabre order Id (it needs to contain at least one valid supplier order Id). |
6 | 100003 | Fulfillment error response: Request for carrier profile cannot be processed to due to timeout or failure. | Your credentials lack access to fulfillment (ticketing) capabilities. | Contact you Sabre account team for assistance. |
7 | 100003 | Fulfillment error response: Order XXXXXXXXX currently being Updated - please Retry again | The air supplier is currently modifying/updating the order you attempted to update. |
1. Wait at least 500 milliseconds and resend the request. 2. Contact Sabre support if the error persists. |
8 | 100003 | Fulfillment error response: farelogixTimeout timed-out and fallback failed. | Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
9 | 100007 | Response processing failed. Unknown Processing status | Temporary internal processing error. |
1. Retry your request. 2. Contact Sabre support if the error persists. |
10 | 500900 | $INVLD - INVOICE FUNCTIONS RESTRICTED, actionId = | Error occurs because the PCC/TJR used does not have full ticketing/invoicing capabilities. | Validate that your PCC/TJR settings are capable of issuing air tickets. In doubt, contact your Sabre account team. |
11 | 500900 | $INVLD - TICKET NUMBER IN USE, actionId = | Order Id was already fulfilled (ticketed). | Validate the Sabre order Id used in the request. |
/orders/view API
# | Code | Error | Cause | Resolution |
---|---|---|---|---|
1 | N/A | {\"category\":\"ERR.PNRDS.CLIENT.VALIDATION_FAILED\",\"message\":\"Message validation failed. Errors: [cvc-complex-type.2.4.b: The content of element 'LocatorWithDate' is not complete. One of '{createDate}' is expected.]\",\"status\":\"NotProcessed\",\"type\":\"Validation\",\"source\":\"CLIENT\"} | Invalid Order Id | Validate the value entered in the "id" field is a valid Sabre order Id. |
2 | 060119 | Unknown error | Invalid or expired order Id. | Validate the value entered in the "id" field is a valid Sabre order Id. |
3 | 500306 | No PNR in AAA | Invalid Order Id | Validate the value entered in the "id" field is a valid Sabre order Id. |
/orders/cancel API
# | Code | Error | Cause | Resolution |
---|---|---|---|---|
1 | 060127 | Order fulfilled | You are attempting to cancel an order that has already been fulfilled, cancellation of fulfilled orders is not available as part of the current release. | The current release does not provide support for cancellations of fulfilled orders. Reach out to the supplier directly if you need to cancel a fulfilled order. |
Frequently Asked Questions (FAQs)
What is the sequence for handling errors in my application?
It is recommended that you design your client code to look for system errors first, then provide error handling, and finally examine the data returned in the response. By first ensuring that errors are not returned, the problem of trying to parse an error instead of response data is avoided.
What should I capture in my log files for SOAP APIs?
When you capture <faultcode>/<faultstring> in your log files, it is suggested that you also include <eb:MessageId> returned with the SOAP envelope of the response. Providing the message ID along with <StackTrace> is helpful if you need to contact our technical support team.