Cookie

    We use cookies and similar technologies. By clicking OK you agree to this. Learn more

    GDS

    Amadeus Enterprise API: Stateless vs. Stateful Explained


    Introduction

    The Amadeus Enterprise API offers both stateless and stateful APIs to cater to different use cases in travel technology. Here's a breakdown of their purposes.

    Stateless APIs

    • Purpose: Designed for simple, one time requests where each API call is independent and does not rely on previous interactions.
    • Characteristics:
      • No session persistence; each request contains all necessary data.
      • Faster and more scalable since no server side state is maintained.
      • Suitable for lightweight queries where context is not required.

    Common use cases for Amadeus stateless APIs

    • Flight Search & Availability : Returning real time flight options based on user input.
    • Hotel & Car Rental Search : Fetching available options without maintaining session data.
    • Pricing & Fare Rules : Providing cost breakdowns for selected flights or services.

    Stateful APIs

    • Purpose: Used for multi-step workflows where context and session persistence are required.
    • Characteristics:
      • Maintains a session (e.g., shopping cart, booking flow).
      • Requires session tokens to track user actions.
      • More complex but necessary for transactional processes.

    Common use cases for Amadeus stateful APIs:

    • Flight Booking & Ticketing: Keeping track of a reservation process across multiple steps.
    • Passenger Name Record (PNR) Management: Storing and modifying travel reservations.
    • Payment & Confirmation: Handling transactions where session persistence is necessary.

    Key Differences

    Feature

    Stateless API

    Stateful API

    Session

    No session

    Session based

    UseCase

    Simple lookups

    Multi-step bookings

    Scalabily

    High (no server state)

    Lower (server tracks state)

    Example

    Airport search

    Flight booking flow

    When to Use Which?

    • Use Stateless APIs for quick searches, reference data or when you don’t need a persistent booking flow.
    • Use Stateful APIs for end to end travel bookings where user selections (e.g., flights, seats, payments) must be tracked.

    Supercharge Your Travel Operations with Seamless Tech, Don’t Wait - Contact Us Today and Let’s Make It Happen!

    0