GDS API Documentation – Galileo & Amadeus

Free GDS API documentation for Galileo and Amadeus command integration

Our GDS API is a single command-based interface that speaks both Galileo (Travelport) and Amadeus. Issue tickets, manage PNRs, and automate travel workflows — from the same endpoint.

Version 1.0 — Production Ready Supports Galileo 1G & Amadeus 1A ✔ Completely Free to Use

GDS API Overview

The GDSHub GDS API provides a command-based interface to the two major Global Distribution Systems — Galileo (Travelport) and Amadeus. It handles flight availability, passenger name records, payment methods, ticket issuance, and reissues. Every request is a POST; every response is JSON.

With our GDS API, you send the same kind of command you would type at a live GDS terminal — the GDS API routes it to the correct system based on the command syntax. To obtain your personal API key, log in to your account and generate credentials from your dashboard.

🆓 Free GDS API: The GDSHub GDS API is offered at no cost — no hidden charges, no subscription fees, and generous usage for development and production. We believe in giving developers and travel professionals open access to GDS data.

Authentication for the GDS API

Every request to the GDS API must include your registered email and API key.

ParameterDescriptionRequired
emailYour registered email addressYes
api_keyYour personal GDS API key (generate from your dashboard)Yes
actionMust be execute_commandYes
commandThe GDS command in either Galileo or Amadeus syntax (e.g. an26MAYSHJCAI for Amadeus, A26MAYSHJCAI for Galileo)Yes
Note: The request_count is automatically incremented for each successful GDS API call. Monitor your usage from your account dashboard.

GDS API Endpoint

POST https://gdshub.pro/account/api/v1/1t/1t

All GDS API requests must be sent via POST with Content-Type: application/x-www-form-urlencoded or application/json.

Command Comparison — Amadeus vs Galileo in the GDS API

Below is a side-by-side reference of the essential booking commands in both systems. The GDS API accepts either syntax — it detects which one you are sending.

PurposeAmadeus (1A)Galileo (1G)
Search flights (SHJ → CAI, 26 May)AN26MAYSHJCAIA26MAYSHJCAI
Sell one seat in Y class on segment 1SS1Y101Y1
Add passenger nameNM1MOUSSA/MAHMOUDN.MOUSSA/MAHMOUD
Agency contact / default PTAAPP.T*
Ticketing agreementTKOKT.T*
Received from (agent / client reference)RFMR.M
End & save transactionERER
Itinerary pricingFXPFQ
Tip: The order matters. In both systems, you search → sell → add name → add contact → ticketing agreement → received from → end transaction (ER) → price → payment → issue. Ending the transaction before you price is what saves the PNR to the system.

GDS API Response Format

A typical success response from the GDS API contains success, output (the command result), and session data (current PNR, segments, etc.).

✅ Successful ticket issuance:
{
  "success": true,
  "output": "TICKET ISSUED SUCCESSFULLY\nPNR: 32JBQP\nPASSENGERS: 1 | SEGMENTS: 1\nTOTAL AMOUNT: AED 2,340.00\nBASE FARE: AED 1,650.00\nTAX: AED 690.00\n\nTICKET NUMBERS:\nPAX 1: 869-7041540806",
  "session": []
}
❌ Error response (missing payment):
{
  "success": true,
  "output": "CANNOT ISSUE TICKET - MISSING ELEMENTS:\n• NO VALID PAYMENT METHOD SET\n\nMissing:\nNAMES, PAYMENT METHOD, AP, PRICE, TICKETING",
  "session": []
}

GDS API Code Examples

Ready-to-run examples in popular languages for the GDS API. Replace the email and API key with your own. The command field accepts either Amadeus or Galileo syntax.

curl -X POST https://gdshub.pro/account/api/v1/1t/1t \
  -d "[email protected]" \
  -d "api_key=YOUR_API_KEY" \
  -d "action=execute_command" \
  -d "command=an26MAYSHJCAI"
<?php
$data = [
    'email'    => '[email protected]',
    'api_key'  => 'YOUR_API_KEY',
    'action'   => 'execute_command',
    'command'  => 'FXP'    // Amadeus pricing. Use 'FQ' for Galileo.
];

$ch = curl_init('https://gdshub.pro/account/api/v1/1t/1t');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);

echo $response;
?>
import requests

url = "https://gdshub.pro/account/api/v1/1t/1t"
payload = {
    "email": "[email protected]",
    "api_key": "YOUR_API_KEY",
    "action": "execute_command",
    "command": "TTP"     # Amadeus ticket issue. Galileo equivalent: "T.T*"
}

response = requests.post(url, data=payload)
print(response.json())
const axios = require('axios');

const params = new URLSearchParams();
params.append('email', '[email protected]');
params.append('api_key', 'YOUR_API_KEY');
params.append('action', 'execute_command');
params.append('command', 'an26MAYSHJCAI');   // or Galileo: 'A26MAYSHJCAI'

axios.post('https://gdshub.pro/account/api/v1/1t/1t', params)
  .then(res => console.log(res.data))
  .catch(err => console.error(err));
#!/bin/bash
EMAIL="[email protected]"
API_KEY="YOUR_API_KEY"
COMMAND="SS1Y1"    # Amadeus sell seat. Galileo: "01Y1"

curl -X POST https://gdshub.pro/account/api/v1/1t/1t \
  -d "email=$EMAIL" \
  -d "api_key=$API_KEY" \
  -d "action=execute_command" \
  -d "command=$COMMAND"
require 'net/http'
require 'uri'

uri = URI('https://gdshub.pro/account/api/v1/1t/1t')
params = {
  email: '[email protected]',
  api_key: 'YOUR_API_KEY',
  action: 'execute_command',
  command: 'ER'      # Same in both Amadeus and Galileo
}

response = Net::HTTP.post_form(uri, params)
puts response.body
package main

import (
    "fmt"
    "io"
    "net/http"
    "net/url"
)

func main() {
    data := url.Values{}
    data.Set("email", "[email protected]")
    data.Set("api_key", "YOUR_API_KEY")
    data.Set("action", "execute_command")
    data.Set("command", "FXP")  // Amadeus pricing. Galileo: "FQ"

    resp, _ := http.PostForm("https://gdshub.pro/account/api/v1/1t/1t", data)
    defer resp.Body.Close()
    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}

GDS API Tips & Best Practices

  • Session persistence: The GDS API maintains a session per email — you can run a sequence of commands (search → add name → payment → ticket) without losing context.
  • Command chaining: Multiple commands can be sent in one GDS API request by separating them with semicolons. Amadeus example: command=NM1AHMED;SS1Y1;FPCASH;TTP. Galileo example: command=N.AHMED;01Y1;F.S;T.T*.
  • Error handling: Always check the success field in the GDS API response. The output field contains human-readable messages from the GDS.
  • Rate limiting: Your request_count is tracked; if you need higher limits, contact support.
  • Mixing systems: Don’t mix Amadeus and Galileo syntax in the same GDS API session — pick one and stay with it. The session context is tied to the GDS that served the first command.
  • End-to-end example: For a complete Python workflow covering flight search, pricing, order creation, and PNR handling, read our guide to automating ticketing with the Amadeus API.