This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.
Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema,
apis.json,llms.txtand similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.
Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.
- Something wrong? Open an issue on this repository, or email info@apievangelist.com.
- Published something new? Ask for a re-score and we will re-run the rating.
- Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.
Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.
On a security or compliance team? Email info@apievangelist.com with security in the subject line and you will get a person, not a form. We will tell you exactly which public URLs this profile was built from so your team can see the same surface we did, and we will take the listing down on request while you work through it.
Full detail: Where this data comes from
American Express Global Business Travel (Amex GBT, NYSE GBTG, headquartered in New York) is the largest business-to-business travel platform in the world, operating in more than 140 countries under the Amex GBT, Egencia and Ovation brands, with CWT acquired in September 2025. Its home market is the United States. In the travel distribution chain Amex GBT is an intermediary rather than a supplier — a travel management company that aggregates air, hotel, rail, car and ground content sourced through the GDS layer, through NDC and through direct supplier connections, then resells it to corporate travel programmes with policy, approval, duty-of-care and reporting wrapped around it. It holds no inventory of its own, but it does hold the booking record, and that is where the switching cost lives. Its API posture is genuinely open at the documentation layer and firmly closed at the runtime layer. The Egencia Developer Center publishes thirteen named APIs and SPIs, and every one of them serves a real, anonymously retrievable OpenAPI 3.1.0 document from apis.egencia.com — no login, no key, no click-through. The identity surface is standards-based (SCIM 2.0 user provisioning over OAuth 2.0 client credentials); the booking, approval, expense, receipt, duty-of-care and reporting surfaces are proprietary Egencia shapes with no OpenTravel, HTNG or IATA NDC schema anywhere in them. Runtime access is customer-account gated — Egencia's own documentation states that "the values for client id and client secret will be provided to the Client after on-boarding to Egencia API platform", and every production endpoint returns 401 to an anonymous caller. So — public contracts, gated runtime, a real documented bulk data export in the BI Transactions API, and API terms Egencia reserves the right to change in its sole discretion.
APIs.json: https://raw.githubusercontent.com/api-evangelist/amex-gbt/refs/heads/main/apis.yml
- Travel
- United States
- Corporate Travel
- Travel Management
- Business Travel
- Distribution
- Booking
- Aviation
- Hotels
- Rail
- Car Rental
- Expense
- Duty of Care
- Reporting
- Created: 2026-07-28
- Modified: 2026-07-28
SCIM-based user provisioning for an Egencia corporate travel programme. Egencia's own overview states the API "supports SCIM, or System for Cross-domain Identity Management, an open standard that allows automating user provisioning using REST API and JSON" and that it "follows version 2.0 of the SCIM protocol". Three concurrent versions are published — /scim/v1/users, /scim/v2/Users and /scim/v3/Users — supporting create, retrieve, search, replace, patch and delete of traveller profiles, with an Egencia SCIM extension schema (urn:ietf:params:scim:schemas:extension:egencia:2.0:User) carrying companyId, singleSignOnId, arrangers, approvers and custom data fields.
- Human URL: Developer Center — User Sync API
- Base URL:
https://apis.egencia.com/openconnect/api
Single sign-on entry point that carries contextual data into the Egencia booking flow at authentication time. Documented endpoints are GET /v1/newTrip and GET /v2/startTrip, which accept trip context and custom data fields such as TravelRequest, PurchaseOrder and MissionOrder, pre-populate the search form and checkout, and flow that context back out through the Expense SPI.
- Human URL: Developer Center — Context SSO API
- Base URL:
https://apis.egencia.com/openconnect-sso-service
Retrieves company information for an Egencia corporate account — name, display name and related detail — plus e-commerce settings and an audit view of those settings.
- Human URL: Developer Center — Company Info API
- Base URL:
https://apis.egencia.com/openconnect/api
Manages custom data fields — the client-defined fields Egencia describes as capturing "invoicing, reporting, approval, billing" detail, commonly department, billing unit, reason for travel or project code. A customer's own cost-allocation taxonomy is modelled inside Egencia's schema and keyed by Egencia definition and value IDs.
- Human URL: Developer Center — Company CDF API
- Base URL:
https://apis.egencia.com/openconnect/api
A service provider interface, not a consumable API — Egencia calls the customer. At checkout Egencia posts the booking payload to a web service the customer must build, and the customer's response authorises or blocks the booking. Published contract: POST /v1/validateFields.
- Human URL: Developer Center — Validation SPI
- Base URL:
https://apis.egencia.com/openconnect-validation-service
Near real-time push of booking and expense data out of Egencia into a customer's expense or ERP system, carrying either receipt or invoice information depending on company configuration, with retries if the consumer does not acknowledge.
- Human URL: Developer Center — Expense SPI
- Base URL:
https://apis.egencia.com/openconnect-expensestream-service
Retrieval of a booking and its individual trip items, plus the receipts attached to an item, paired with a Get Booking SPI push notification. Booking and item identifiers are Egencia keys; the supplier PNR and record locator travel with the data.
- Human URL: Developer Center — Booking API
- Base URL:
https://apis.egencia.com/openconnect/api
Trip-level cancellation and deletion of bookings — POST /v1/bookings/{bookingId}/cancel and /delete — acting on every trip item in the booking.
- Human URL: Developer Center — Cancellation and Deletion API
- Base URL:
https://apis.egencia.com/openconnect/api
Programmatic approval or denial of booking requests, at trip level and at trip-item level.
- Human URL: Developer Center — Approval API
- Base URL:
https://apis.egencia.com/openconnect/api
An outbound service provider interface that lets a customer decide, at checkout time, whether level one and level two approval are required and who the approvers are. Published contract: POST /v1/custom-approval.
- Human URL: Developer Center — Approval Customisation SPI
- Base URL:
https://apis.egencia.com/openconnect/api
Retrieval of the receipt for a booked trip item via GET /v1/receipts/{itemId}, paired with a Receipt SPI push whose documented payload carries booking_id, item_id, product_type, company_id, traveler_id, organization_parent_id and a HAL-style _links.receipt href back into the Egencia API.
- Human URL: Developer Center — Receipts API
- Base URL:
https://apis.egencia.com/openconnect/api
Traveller-tracking data for risk and duty-of-care programmes — POST /v1/bookings creates a paginated query of booking data for a partner ID over a date range, then GET /v1/bookings/{resourceId} pages the result.
- Human URL: Developer Center — Duty of Care API
- Base URL:
https://apis.egencia.com/dutyofcare/api
Consolidated booking transaction data out of Egencia, and the closest thing in the estate to a documented exit path. POST /v1/transactions creates a filtered report over a date range and returns pagination links; GET /v1/transactions/{reportId} pages the result. Line-of-business variants cover air, hotel, car, train, ground and fees. Response schemas carry pnr, record_locator, marketing/operating/ticketing carrier codes, hotel_chain_code, ticket_code, confirmation_number and invoice_number alongside Egencia's own itinerary_number. A separate GET /v1/egencia_iata returns the IATA agency code for a point of sale, and an is_ndc flag records whether an air booking was made through NDC.
- Human URL: Developer Center — Reporting API
- Base URL:
https://apis.egencia.com/bi/api
- Website
- Developer Portal
- Documentation
- Authentication — OAuth 2.0 client credentials
- OpenConnect service definition
- BI service definition
- Duty of Care service definition
- Company service definition
- Postman Collection
- Egencia
See review.yml for the full evidence trail. In summary:
- Interface shape: standard-plus-proprietary. SCIM 2.0 and OAuth 2.0 are real and load-bearing on the identity surface; everything else is a bespoke Egencia shape with no OpenTravel, HTNG or NDC schema.
- Second source: alternatives-with-migration. BCD Travel, CTM, Navan, TravelPerk, SAP Concur Travel and CWT (now owned by Amex GBT) are real substitutes, but none of them speaks Egencia's booking, CDF or reporting shapes.
- Exit path: bulk-export-documented —
POST https://apis.egencia.com/bi/api/v1/transactions, paginated viaGET /v1/transactions/{reportId}. ADELETE /gdpr?user_id=erasure operation exists on every service; it deletes, it does not export. - Identifier portability: PNR / record locator, IATA agency code per point of sale, carrier codes and hotel chain codes travel; Egencia
itinerary_number,booking_id,item_id,company_id,traveler_idand SCIMuserIddo not. - Access gate: customer-account-required. "The values for client id and client secret will be provided to the Client after on-boarding to Egencia API platform."