canonical: https://jentic.com/apis/amadeus.com/amadeus-flight-check-in-links # Amadeus Flight Check-in Links The Amadeus Flight Check-in Links API returns the official online check-in URL for a given carrier, by IATA code. The single GET endpoint at /reference-data/urls/checkin-links accepts an airline IATA code and an optional language and returns the carrier's web check-in entry point, so itinerary emails and trip-detail screens can deep-link travellers straight to the right place. It is a small but high-value lookup that removes the need to maintain a hand-curated table of carrier check-in URLs. ## For AI agents Return the official online check-in URL for an airline by IATA code. Agents call /reference-data/urls/checkin-links to deep-link travellers directly into web check-in. ## Scope Does not perform check-in, return seat maps, or issue boarding passes - use only to retrieve the carrier's official online check-in URL. ## Capabilities - Return the official check-in URL for a carrier by IATA code - Localise the response by passing a language parameter where the carrier supports multiple locales - Power 'check in now' deep links in itinerary emails and travel apps - Replace hand-curated check-in URL tables that drift out of date - Surface the right URL for code-share carriers by passing the operating carrier's IATA - Drive in-app web check-in nudges 24 hours before departure ## Use cases ### Trip-Detail Deep Links Travel apps and itinerary screens want a one-tap 'Check in now' button that goes to the carrier's official web check-in page. The /reference-data/urls/checkin-links endpoint returns that URL given the carrier IATA code, so the app can deep-link the traveller directly without the user hunting for the right airline.com URL. The lookup is cheap enough to call inline when rendering the trip detail. Example prompt: Call /reference-data/urls/checkin-links with airlineCode=BA and return the official check-in URL. ### Pre-Flight Reminder Emails Itinerary platforms send a 'time to check in' email roughly 24 hours before departure. To make the call to action useful, the email needs the carrier's actual check-in URL, not a generic search link. The check-in links endpoint provides exactly that, keyed by IATA code, so the reminder email service can populate the link at send time without maintaining a list of carrier URLs internally. Example prompt: For every itinerary departing in 24 hours, fetch the check-in URL for the operating carrier and inject it into the reminder email. ### Localised Travel App Experience Travel apps with a German or French audience can request the localised check-in URL by passing the language parameter. The carrier returns the right locale variant of its check-in page, which gives travellers a smoother handoff than the default English page. Combine with the user's app language setting to pick the right locale automatically. Example prompt: Fetch the German-language check-in URL for LH and use it as the deep link for German-locale users. ### Agent Departure Coordinator An AI travel assistant nudging a user toward their flight can call check-in links automatically once it has the operating carrier from the itinerary. Through Jentic the agent searches for 'get airline online check-in url', loads the schema, executes the lookup, and returns the URL to the user with a friendly reminder. No carrier-URL table to maintain in the agent's prompt. Example prompt: Use Jentic to fetch the check-in URL for the carrier on the user's itinerary and return it with a 'check in opens at' message. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /reference-data/urls/checkin-links | Return the check-in URL for an airline | ## Key resources - **Check-in Links** — GET the official online check-in URL for a carrier by IATA code. ## Why Jentic - **Setup:** Wiring the Flight Check-in Links API by hand means handling the Amadeus OAuth 2.0 client_credentials exchange, refreshing the bearer token, and calling GET /reference-data/urls/checkin-links against the correct Amadeus host and version. Through Jentic you install once, import Flight Check-in Links from the API Directory, store the Amadeus client credentials once, and your agent calls it. - **Permission scoping:** The airline code and language travel as query parameters, not as a resource id in the URL path, so scoping is by operation. You limit the agent to the operations it needs, such as reading a carrier's official check-in URL, and it cannot reach other Amadeus operations unless you add them. - **Credential handling:** Your Amadeus client_id and client_secret are stored once, encrypted, by your own Jentic One instance, which performs the client_credentials exchange and injects a fresh bearer token at execution time. The raw secret never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get the online check-in URL for British Airways', and Jentic returns the /reference-data/urls/checkin-links operation with its input schema so the agent supplies the airline code without scanning the Amadeus docs. ## Related APIs - **Amadeus Airline Code Lookup** — Resolves the IATA code into a carrier name to display alongside the check-in link. - **Amadeus On-Demand Flight Status** — Returns live flight status which can drive when to send a check-in reminder. - **Amadeus Flight Availabilities Search** — Surfaces the operating carrier whose check-in URL the lookup retrieves. ## FAQ ### What authentication does the Flight Check-in Links API use? The API uses the Amadeus OAuth 2.0 client-credentials flow. Exchange API key and secret at the Amadeus token endpoint and send the bearer token on the /reference-data/urls/checkin-links request. Jentic stores the credentials in the encrypted vault and refreshes the token automatically. ### Does the response include localised URLs? Yes, where the carrier supports multiple languages. Pass a language parameter on the request and the API returns the locale-appropriate check-in URL when the carrier publishes one. If only a default URL exists, that is what the API returns. ### What are the rate limits for the Flight Check-in Links API? Rate limits are not declared in the OpenAPI spec and depend on the Amadeus contract tier. The endpoint is read-only and the response is cacheable for hours, so cache per IATA code and language to stay well under the per-second cap on production traffic. ### How do I add a check-in link through Jentic? Run pip install jentic, then use the search query 'get airline online check-in url'. Jentic returns the /reference-data/urls/checkin-links operation, you load the schema, supply airlineCode and language, and execute. The URL drops straight into your trip-detail UI or reminder email. ### Which carrier should I pass for a code-share flight? Pass the operating carrier's IATA code, not the marketing carrier - passengers check in with the airline that actually operates the aircraft. The operating carrier is part of the flight segment data returned by Flight Offers Search and similar endpoints. ### Is the Flight Check-in Links API free? Amadeus self-service APIs include a free test environment with quota limits and a paid production tier. Production access is contracted with Amadeus and pricing scales with transaction volume - check current rates in the developer portal. ### Can I limit what my agent is allowed to do with the Amadeus Flight Check-in Links API? Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and scoping here is by operation since the airline code and language travel as query parameters rather than a resource id in the path. You can allow the agent only to read a carrier's official check-in URL through GET /reference-data/urls/checkin-links, so it cannot reach any other Amadeus operation unless you add it. Your Amadeus client credentials stay stored and encrypted by your own instance, and the token is injected at execution time rather than exposed to the agent.