# Travelport TripServices APIs > Travelport TripServices is a set of REST JSON APIs on the Travelport global distribution system. It searches, prices, books, tickets, exchanges and cancels flights, books and cancels hotel stays, and authorises payment cards, for travel sellers under contract. - Canonical: https://www.anchorterminal.com/tools/travelport - Markdown: https://www.anchorterminal.com/tools/travelport.md (~7,700 tokens) - Slim: https://www.anchorterminal.com/tools/travelport.min.md (~1,730 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/travelport.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade E · 45.9/100 · rank #653 of 722 · #6 in Travel & booking · not agent-ready · confidence medium** ## Assessment Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission. ## Facts | Field | Value | | --- | --- | | Vendor | Travelport (https://www.travelport.com) | | Kind | HTTP API | | Category | Travel & booking (https://www.anchorterminal.com/categories/travel) | | Transport | HTTP | | Endpoint | `https://api.travelport.net` | | Auth | OAuth · OAuth 2.0 with the password grant. A POST to `https://auth.travelport.net/oauth/token` (pre-production `https://auth.pp.travelport.net/oauth/token`) with `username`, `password`, `client_id` and `client_secret` returns a Bearer token valid for 24 hours. Every call also carries `XAUTH_TRAVELPORT_ACCESSGROUP` or `TVP-PCC-CORE`, which sets the point of sale and the content the caller may reach. Trial credentials are requested on a form at my.travelport.com and arrive by email. Production credentials come after a contract through sales and certification, and are managed in the Credential Access Manager in MyTravelport, which creates, rotates and disables primary and managed identities. No scopes were found. | | Pricing | Paid (Paid) · No public price. The API and SDK Terms of Use say charges are set in each Developer Contract and invoiced monthly, and the docs send new customers to sales. A trial with no payment exists for building against realistic air shopping, requested through a form that asks for a name, work email and company. Production access is per contracted API after certification (checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the developer portal, the three OpenAPI files or the terms (checked 2026-10-08). | | Licence | Proprietary service under a Developer Contract and Travelport's API and SDK Terms of Use | | Docs | https://developer.travelport.com/ | | llms.txt | https://developer.travelport.com/llms.txt | | Last release | 2026-08-12 | | APIs | Flights (OpenAPI 3.0, version 11.36.0, 101 operations), Stays (11.36.0, 22 operations, with a version 12 SearchComplete flow) and Pay (11.34.0, 2 operations) | | Hosts | Production `https://api.travelport.net/11/air/`, `/11/hotel/`, `/12/hotel/` and `/11/payment/`. Pre-production on `https://api.pp.travelport.net`. Tokens from `https://auth.travelport.net/oauth/token` | | Content | Travelport says 400+ airlines across GDS, NDC and low-cost carriers, and hotels in 180 countries, including Expedia and Booking.com content where provisioned | | Flights workflow | Search, price, add to a reservation workbench, commit, ticket, then exchange, refund or void. Seats, ancillaries and EMDs are covered | | Stays workflow | Property search, availability, rules, book, retrieve, modify and cancel | | Credentials | OAuth 2.0 password grant, 24-hour Bearer token, access group or PCC header on every call. Primary and managed identities in the Credential Access Manager | | Rate limits | 50 token requests a second per IP address. No limit for the Flights, Stays or Pay calls was found in the docs | | Session times | Search results cached 12 minutes for GDS and 34 minutes for NDC content. A workbench lasts 30 minutes | | Errors | `Result/Error` and `Result/Warning` with StatusCode, Message, SourceID, SourceCode and Category, and published code ranges by area. Stays has an older two-field form for some customers | | Access | Trial credentials by form with no payment. Production by sales contract, then certification with at least 15 days' notice | | Developer kits | Postman collections for NDC and GDS flights (v26.11.1), Stays (August 2026) and Pay. No SDK or MCP server found | | Support | Cases and Developer Advisories through MyTravelport, which needs a customer login | | Data retention | The GDS privacy notice says booking data is destroyed no more than 36 months after the last travel transaction in a reservation | | Capabilities | travel.flights, travel.stays, travel.booking, travel.changes, travel.search | | Tags | hosted, closed-source, enterprise, sales-led, oauth, openapi, llms-txt, gds, ndc, trial | | JSON | https://www.anchorterminal.com/api/v1/tools/travelport.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 19 | 3.8 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 84 | 13.7 | | Agent ergonomics | 13% | 16.2 | 51 | 8.3 | | Security & auth | 14% | 17.5 | 47 | 8.2 | | Payments & pricing | 10% | 12.5 | 20 | 2.5 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 56 | 4.9 | | Transparency & trust (editorial 47, provenance 57) | 7% | 8.8 | 52 | 4.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **45.9 → E** | ### Why each score - Reliability 19: Graded as a hosted API. No public status page found. None is linked from the developer portal or the support page, and status.travelport.com did not answer (0). No readable incident history, so 5 by the rubric (5). The only published limit is 50 token requests a second per IP address. No limit for the Flights, Stays or Pay calls was found (4 of 15). No 429, Retry-After or backoff guidance and no idempotency key for booking or ticketing was found in the docs or the three OpenAPI files, whose responses list 400, 401, 402, 403, 404, 500 and 503 only (0). No SLA published, and the test terms disclaim availability (0). Version 11 is in production and the docs say TripServices is ready today (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 84: Public OpenAPI 3.0 files download without login for Flights (version 11.36.0, 101 operations), Stays (22) and Pay (2) (25). `llms.txt` lists the docs, and every page has a Markdown copy at the same path with `.md` (10). Long guides explain search, pricing, booking, ticketing and exchanges and when each call applies, but 35 of the 101 Flights operations have no description in the spec (13 of 20). Typed schemas with required fields, patterns and length limits, 130 enums in Flights, and polymorphic `@type` objects. Travelport warns the files may hold unmapped roadmap objects, and the Stays FAQ says Postman and the spec disagree on some names (11 of 15). 2,237 examples in the Flights spec and published error lists with code ranges, though Pay has no error list (12 of 15). The version sits in the path with `Accept-Version` and `Content-Version` headers, and release notes are dated per API. The portal's changelog page is empty (13 of 15). - Agent ergonomics 51: `offersPerPage`, `maxNumberOfUpsellsToReturn`, detail-view flags and reference payloads (an identifier in place of the full fare) size a request, but responses are large nested documents with no field selection found (15 of 25). Stays paginates with a `nextIdentifier`, Flights caps results per page, and search filters cover carriers, cabins and content source (15 of 20). Errors carry StatusCode, Message, SourceID, SourceCode and Category with documented ranges. Some failures arrive as HTTP 200 with COMMUNICATION ERROR in the body, Stays has two error formats, and a wrong version returns only `faultstring` (13 of 20). No idempotency key or retry guidance was found. The workbench is a two-step build then commit, which keeps a booking uncommitted until the last call (5 of 20). Each call needs a token, an access group or PCC header, compression and often two version headers. There is no SDK, only Postman collections (3 of 15). - Security & auth 47: OAuth 2.0 password grant, with a username, password, client id and client secret exchanged for a 24-hour Bearer token. The Credential Access Manager creates, rotates and disables identities. No scopes were found, and the long-lived secret is a password (20 of 30). Access groups limit a credential to one point of sale and its content, managed identities give third parties their own credentials, and pre-production is a separate host. No read-only credential or approval step for ticketing was found (8 of 20). Responses are mostly structured supplier data, with free text in hotel descriptions, fare rules and remarks and no injection guidance (8 of 15). Every response has an `E2ETrackingId` and a transaction id, and callers can send a `TraceId`. No operator log or audit export is documented (5 of 15). A Responsible Disclosure Policy dated June 2025 with a 10 business day acknowledgement and no bug bounty. Both security.txt paths return 404, and no SOC 2, ISO 27001 or PCI attestation was found on the pages read (6 of 20). - Payments & pricing 20: No x402, MPP or L402 (0). No public price. The terms say charges are specified in each Developer Contract, and the docs send new customers to sales (0). A trial with no payment is advertised on the portal, with credentials sent by email after a form (20). A person fills in the form with a name, work email and company, and production needs a contract and certification (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 56: The newest dated Flights release is Air Offer 26.11.33W on 12 August 2026, updated 25 August, and the release notes page was last modified on 16 September 2026. That is within 90 days and outside 30 (20 of 30). Four dated Flights releases since 10 July 2026, on 16 July, 27 July, 5 August and 12 August (20). Public release notes, with support cases, the knowledge base and Developer Advisories behind a MyTravelport login and no public forum. The Stays page lists no 2026 release (8 of 15 for a closed service). No SDK. The Postman developer kits are current, at v26.11.1 for GDS flights and August 2026 for Stays (5 of 15). No package to judge. The OpenAPI files are at 11.36.0 with older versions kept alongside (3 of 10). - Transparency & trust 52: Closed service. The API and SDK Terms of Use and the test system terms are public, but the Developer Contract that sets charges, liability and the contracting entity is not (13 of 30). The GDS privacy notice, last updated 3 January 2025, lists the traveller data held, says it is destroyed no more than 36 months after the last travel transaction, and states Data Privacy Framework certification for Travelport, LP. No public DPA was found (20 of 30). The API reference marks seven Flights operations as deprecated with no dates, the terms promise reasonable advance notice of changes, and retirement dates go out in Developer Advisories behind a login (8 of 20). No subprocessor list was found. The terms say data may be stored in the United States or any country where Travelport or its agents have facilities, the FAQ says the platform runs on AWS, and a global operator list names the distributor in each country (6 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/travelport.md (JSON https://www.anchorterminal.com/fixes/travelport.json) ### What we couldn't check - unchecked: whether Travelport runs a public status page. status.travelport.com did not answer our request and no status link was found on the portal, so the line is scored as absent - unchecked: the trial's limits (which APIs, how long, what volume). The form sits behind a script-drawn page and the docs describe only air shopping - unchecked: Developer Advisories, the knowledge base and the Credential Access Manager articles, which need a MyTravelport login - Whether written authorisation for AI agent access is granted as a matter of course. The terms bar automated tools without it, while the portal markets TripServices for AI travel - Whether production calls are rate limited and what a throttled response looks like. No limit or 429 was found in the docs or the OpenAPI files - Security certifications such as PCI DSS, ISO 27001 or SOC 2. None was found on the pages read, which is not evidence that none is held - Which Travelport company signs the Developer Contract and under which law. The public terms leave both to the contract ### Sources - developer portal home, trial claim and product list: (seen 2026-10-08) - llms.txt: (seen 2026-10-08) - authentication, hosts and token rate limit: (seen 2026-10-08) - Flights OpenAPI 3.0 file, version 11.36.0: (seen 2026-10-08) - Stays OpenAPI 3.0 file: (seen 2026-10-08) - Pay OpenAPI 3.0 file: (seen 2026-10-08) - Flights release notes: (seen 2026-10-08) - Flights error messaging: (seen 2026-10-08) - common Flights headers: (seen 2026-10-08) - certification checklist: (seen 2026-10-08) - Flights FAQs and best practices (cache and workbench times): (seen 2026-10-08) - Stays FAQ (pagination, tokens, errors): (seen 2026-10-08) - developer kits and downloads: (seen 2026-10-08) - support options: (seen 2026-10-08) - Terms of Service for test system access: (seen 2026-10-08) - API and SDK Terms of Use: (seen 2026-10-08) - Privacy Notice for the GDS: (seen 2026-10-08) - Responsible Disclosure Policy: (seen 2026-10-08) - trial request form (text read from the page's script): (seen 2026-10-08) - security.txt (404): (seen 2026-10-08) - RDAP for travelport.com: (seen 2026-10-08) - official MCP registry search, no result: (seen 2026-10-08) - GitHub organisation repositories: (seen 2026-10-08) ## Who's behind it (provenance 57/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Travelport, LP | 20/20 | | Domain age | travelport.com, registered 2001-09-30 (25 years) | 15/15 | | Endpoint on the vendor's domain | api.travelport.net is not on travelport.com | 0/15 | | Terms of service | read, states 3 of the 7 things a reader expects, and has 2 clauses that cost points | 2.6/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | not found | 0/10 | | Changelog | published | 10/10 | | security.txt | not found | 0/10 | The API and SDK Terms of Use are incorporated into each Developer Contract, which names the contracting Travelport company and sets the charges. The contract itself is not public. Trial and pre-production access falls under the Terms of Service for Travelport test system access on the developer portal, governed by the law of Georgia, USA. The privacy link is the Travelport Privacy Notice for the GDS, last updated 3 January 2025, which covers traveller data processed in the Apollo, Galileo and Worldspan systems. It names Travelport, LP for the Data Privacy Framework, with offices in Langley, Berkshire and Atlanta, Georgia. The APIs answer on api.travelport.net and auth.travelport.net, a second domain named in Travelport's own docs. RDAP gives travelport.net a registration date of 2000-01-12 with Amazon Registrar, and travelport.com 2001-09-30 with CSC Corporate Domains. No status page is linked from the developer portal or the support page. status.travelport.com did not answer our request. www.travelport.com/.well-known/security.txt and the developer portal's both return 404. A Responsible Disclosure Policy dated June 2025 takes reports at responsibledisclosure@travelport.com and says there is no bug bounty. The portal's /changelog page is empty. Dated release notes are kept per API, and the Flights page was last modified on 16 September 2026. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.travelport.com/legal-policies/api-sdk-policies-terms-of-use), read 2026-10-08, gives no date, states 3 of the 7 things a reader expects. - To know. Restricts automated access (costs points). "use any automated process or tool to access and/or use the Service (such as a BOT or a spider) without written authorization from Travelport;" - To know. Says the terms or the service can change without notice (costs points). "7.2 We may automatically transmit updates or upgrades to the software to your computer to update, enhance, and further develop the Service without notice to you." - To know. Says access can be ended without notice or for any reason. "Our cancellation or suspension may be without cause." - Not found in the text. Gives the date it was last updated. - Not found in the text. Names the governing law or courts. - Not found in the text. States a limit on its liability. - Says how changes to the terms are announced. Gives 30 days of notice before a change. - Not found in the text. Refers to a service level or uptime commitment. - Also in the text (2026-10-08). Developers may not use the service to run queries and then complete the bookings through a third party's system. "use the Service to perform queries, but then complete bookings via a third party's system;" - Also in the text (2026-10-08). Travelport may place advertising in results, interfaces and content served through the services, and developers must not omit or obscure it. "We reserve the right to include advertising in the results provided to you via the Services, in any user interface we provide for the Services, or in Content served through the Services." - Also in the text (2026-10-08). Developers must give Travelport reasonable access, without charge, to applications that use the service so it can monitor compliance. "8.2 You will permit us reasonable access, without charge, to the applications that utilize the Service for purposes of monitoring your compliance with these Terms of Use." **Privacy policy** (https://www.travelport.com/legal-policies/privacy), read 2026-10-08, dated 2025-01-03, states 7 of the 8 things a reader expects. - Gives the date it was last updated. Last updated 2025-01-03. - Not found in the text. Says how long data is kept. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. privacy@travelport.com. - Says where data is transferred or stored. Relies on the Data Privacy Framework. ## Live (updated 2026-10-08 22:40 UTC) - Right now: up, HTTP 404, 146 ms, checked 2026-10-08 22:40 UTC (get on `https://api.travelport.net`) - Uptime 24h 100.0% (36 probes) · 30 days 100.0% (36 probes) · p50 158 ms · p95 879 ms - Always current: https://www.anchorterminal.com/api/v1/live/travelport.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Public OpenAPI 3.0 files for Flights (101 operations), Stays (22) and Pay (2), with an llms.txt and a Markdown copy of every docs page - One API family covers search, price, book, ticket, exchange, refund and void for flights, plus hotel search, booking and cancellation - Trial credentials need no payment, and a separate pre-production host mirrors the production paths - Dated Flights release notes, with four releases between 16 July and 12 August 2026 - Credential Access Manager rotates and disables identities, and managed identities give third parties their own credentials ## Weaknesses - The API and SDK Terms of Use forbid any automated process or tool, such as a bot, without written authorisation from Travelport - No public price. Charges sit in a Developer Contract reached through sales, and production needs certification with 15 days' notice - No status page, SLA or API rate limit was found. The only published limit is 50 token requests a second per IP - Tokens come from the OAuth password grant with a username, password, client id and client secret, and no scopes were found - No idempotency key, no SDK and no MCP server. Some failures arrive as HTTP 200 with an error object in the body ## Before you call it (notes for agents) 1. Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason 2. Send `Accept-Encoding: gzip, deflate` and `XAUTH_TRAVELPORT_ACCESSGROUP` (or `TVP-PCC-CORE`) on every call. Production traffic without compression is refused 3. Send `offersPerPage` on a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC 4. Commit a workbench within 30 minutes or it expires, and read `Result/Error` in the body even on HTTP 200 5. Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings ## Connect First request: ```bash curl -X POST https://auth.pp.travelport.net/oauth/token \ -H "Content-Type: application/x-www-form-urlencoded" \ -d "grant_type=password&username=$TP_USERNAME&password=$TP_PASSWORD&client_id=$TP_CLIENT_ID&client_secret=$TP_CLIENT_SECRET" ``` Through letme (picks today, calling later): https://letme.dev/travelport. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Duffel Flights and Stays API | B | 66.7 | 230 | travel.flights, travel.stays, travel.booking, travel.changes, travel.search | no | https://www.anchorterminal.com/tools/duffel.md | | LetsFG | B | 64 | 287 | travel.flights, travel.stays, travel.booking, travel.changes, travel.search | no | https://www.anchorterminal.com/tools/letsfg.md | | LiteAPI (Nuitee Connect) | D | 53.1 | 548 | travel.stays, travel.flights, travel.booking, travel.changes, travel.search | no | https://www.anchorterminal.com/tools/liteapi.md | | ETG API (RateHawk) | D | 53 | 554 | travel.stays, travel.booking, travel.changes, travel.search | no | https://www.anchorterminal.com/tools/ratehawk.md | | FlightClaw | E | 45.3 | 659 | travel.flights, travel.booking, travel.changes, travel.search | no | https://www.anchorterminal.com/tools/flightclaw.md | | Expedia Group Rapid API | E | 42.8 | 674 | travel.stays, travel.booking, travel.changes, travel.search | no | https://www.anchorterminal.com/tools/expedia-rapid.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The API and SDK Terms of Use say a developer shall not use any automated process or tool, such as a bot or a spider, to access or use the service without written authorisation from Travelport (source: ) - The same terms forbid speculative, duplicative or fictitious segments and using the service for queries while completing bookings through a third party's system (source: ) - The developer portal home says "Instant trial access" with no payment required, and the request form's confirmation text says credentials arrive by email within one business day (source: ) - Moving to production means a support case for certification with sample requests and responses, at least 15 days' notice, and a contract for each API (source: ) - A supplier that can't be reached returns StatusCode 200 with the message COMMUNICATION ERROR and SourceCode 2599 in `Result/Error` (source: ) - The Stays FAQ says tokens may not be standard JWTs and should be handled as opaque strings, and that Postman examples and the OpenAPI files disagree on some field names (source: ) - Travelport's GitHub organisation holds only tutorials and samples for the older uAPI, last pushed in July 2022. No TripServices SDK was found (source: ) ## Compare - [Booking.com Demand API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/booking-demand-api-vs-travelport.md): E 38.1 vs E 45.9 - [Expedia Group Rapid API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/expedia-rapid-vs-travelport.md): E 42.8 vs E 45.9 - [Hotelbeds Hotel Booking API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/hotelbeds-vs-travelport.md): F 36.3 vs E 45.9 - [LiteAPI (Nuitee Connect) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/liteapi-vs-travelport.md): D 53.1 vs E 45.9 - [ETG API (RateHawk) vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/ratehawk-vs-travelport.md): D 53 vs E 45.9 - [Duffel Flights and Stays API vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/duffel-vs-travelport.md): B 66.7 vs E 45.9 - [FlightClaw vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/flightclaw-vs-travelport.md): E 45.3 vs E 45.9 - [Kiwi.com MCP Server vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/kiwi-mcp-vs-travelport.md): D 51.9 vs E 45.9 - [LetsFG vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/letsfg-vs-travelport.md): B 64 vs E 45.9 - [Skyscanner Travel APIs vs Travelport TripServices APIs](https://www.anchorterminal.com/compare/skyscanner-vs-travelport.md): E 45.6 vs E 45.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on travelport.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "travelport", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Travelport TripServices APIs on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Travelport TripServices APIs on Anchor Terminal](https://www.anchorterminal.com/badges/travelport.svg)](https://www.anchorterminal.com/tools/travelport) ``` Plain link: ```html Travelport TripServices APIs on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Travelport TripServices APIs is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/travelport-dark.png - Light: https://www.anchorterminal.com/assets/share/travelport-light.png