Ready to Certify?

To certify with any of the JSON APIs, follow the checklist below and then enter a support request in your MyTravelport account.

Travelport requires at least 15 days' notice before you intend to move to our production environment to complete the required checks and allow for possible changes to your application. Travelport provides your production credentials at the end of certification.

In this topic:

• Pre-Certification Checklist

  • Required Information for API Certification Approval

  • Travelport Recommended Best Practices to Consider

• Enter a Support Request for Certification

Pre-Certification Checklist

Prior to submitting a request for an API certification approval, you will need to provide sample API request and responses from your system for the APIs you have developed to for this JSON API Certification. Ensure you have reviewed the following checklist and implemented the following guidelines as part of your development.

For additional information, see the topics in the General menu above on authentication, endpoints, common headers, and - if supported for your APIs - trace and transaction IDs.

Required Information for API Certification Approval

You must provide example request and response messages generated from your system that represents all Travelport APIs you have developed that will be used. The examples provided must include the following scenarios:

For Air API certification:

• Requests with, at minimum, the passenger types adult (ADT), child (CHD), and infant (INF). Ages are required for child and infant PTCs.

• A round-trip An itinerary in which travel goes to a single destination and returns to the origin. E.g., LHR > CDG and CDG > LHR. itinerary The entire trip on a booking, including all flights on all legs. Also called a journey. that includes a connecting flight.

• If you are targeting a specific fare (e.g., private fare Special air fares negotiated by agencies. Private fares may use account names, account codes, contract codes, or corporate IDs. or net fare Net fares, also called consolidator fares or bulk fares, are any negotiated price between an airline and a consolidator or agency. Send your account or corporate code in the search request to receive net fares in the response. GDS only; NDC carriers do not generally offer net fares.) or a fare for a specific account code fare, use that same fare type or account code through the full workflow.

For Hotel API certification:

• Multiple guests including adult and child

• Multiple rooms

• If provisioned for hotel aggregator content, when sending the value from CatalogOffering/Identifier/authority from the Availability response in subsequent references to an offer In the JSON Search APIs, an offer is a product available at a specific price under a set of terms and conditions. An offer includes the flight or connecting flights for one leg of the itinerary, plus a service level that includes the cabin class and any fare codes that may apply. At booking, the selected offer from the Search response - including the flight/s, service level, price, terms and conditions, and brand if applicable - is converted into a single Offer object that is subsequently returned for that booking., the value must be either EXPE (Expedia) or BKNG (Booking.com). For more information see the Availability API Reference.

For all APIs, check that all examples included in your API certification request follow these standards:

1. All object values are correct according to their Swagger definition, e.g., string, Boolean, integer, enum, etc.

2. A complete and proper response message based on your API request message submission is returned and included.

3. Message examples should contain the type of content and full set of API workflow messages you plan to make available and want to be certified against. For example, for Air API certification, if you want to be certified to book only GDS Global Distribution System. A GDS aggregates and distributes air, hotel, and car rental content such as schedules, fares, and upsells. In the JSON APIs, GDS content is distributed from Travelport. air content and not NDC New Distribution Capability, an XML standard for exchanging data that supports airlines in distributing their content directly to online travel agencies. See the NDC Guide. air content, your Search request should send only the value "GDS" in the contentSourceList object and the response example should contain only GDS offers.

4. All examples must include the full URL endpoints used and include the correct base, context path, and version of the API.

5. All examples should provide the message headers used with each request and the following details must be available for review and included:

   • All API request headers must show they have compression applied.

   • All API request headers must include the correct version in the content-version and accept-version are included.

6. In addition, also provide written documentation of when and how often your system will perform a token refresh. Note: Token refresh in excess of the recommended once every 23 hours is reason for Travelport to decline API certification unless an exception is needed and the reason is provided.

Travelport Recommended Best Practices to Consider

For the Air APIs, Travelport recommends sending in your examples with a custom trace ID in the request of all APIs that support it. This is a best practice for future troubleshooting if necessary. See Trace and Transaction IDs. (The Hotel APIs do not support the trace ID, but do return a transaction ID A tracking id returned in the transactionId object under the first top-level object of every response in the JSON APIs. This system-generated ID assists Travelport and customers with troubleshooting if needed. In addition, developers can send a custom traceId in the header as their own tracking number. See Transaction and Trace IDs on the General menu. for the Hotel Standard Availability API.)

Validate that all modifiers you plan to use are supported for the version of the JSON API being consumed.

Verify that object values make sense. For example, for Air searches, if you specify a permitted airline, that same airline cannot also be sent in the prohibited list.

Validate that object structure such as lists and hierarchies or parent and child objects are used properly.

If the API uses query parameters, verify they are sent correctly per the API reference for that request.

Verify that API response messages always return a unique E2ETrackingID in the header of the response.

Enter a Support Request for Certification

Follow these steps when you ready to certify that your workflow/s are production-ready:

1. Raise a case, following these steps:
   • If you are not already logged into the Developer Experience website, access it at https://developer.travelport.com/
   • Check that your initials appear in the upper-right corner of the page to ensure you are logged in. Log in if necessary.
   • At the top of the screen select Resources > Support portal.
   • Click Raise a Case.
   • Click Developer Product Services.
   • Select Certification from the Problem Type dropdown.
   • Select RESTful JSON API Microservices (formerly Trip Services) from the Product dropdown.
   • Provide applicable details for your request under Please give us additional information about the issue. Travelport will contact you if additional information is needed.
   • In the Web Service URL field enter N/A.
   • Click Submit.
   • Note the assigned case number, which begins with the letters CS. You need that number in the next step.
2. A representative will contact you via your case number.