Request parameters explained

Parameters and response fields that are commonly misunderstood.

Terms: GDS/PSS (Global Distribution System / Passenger Service System) — the airline reservation or host system (Amadeus, Sabre, Galileo, and airline PSS) holding the ticket. EMD (Electronic Miscellaneous Document) — a document for ancillary services (seats, baggage), as opposed to an e-ticket for flights.

isEmd

A routing hint only — it does not control how a document is treated. Deal Engine determines the real document type from GDS/PSS data (the presence of an RFISC, the service code identifying an EMD):

• isEmd: true on an actual e-ticket is not rejected and produces no error.
• The engine silently corrects the flag and processes the document as its real type.
• The response reflects the actual document type.

You cannot force EMD treatment through isEmd. Trust the GDS/PSS-derived type in the response.

Related document references

Document responses may reference other tickets. All are read-only context — the refund is always keyed to the ticketNum you requested, and none require action:

The Sync header

Behaves differently per mutation — the part most integrators get wrong:

• createQuote — Sync: true waits (up to ~30 s) and returns the full quote results. Genuinely synchronous.
• processRefund — Sync: true only delays the response. The body remains the enqueue acknowledgment:

{ "success": true, "message": "Queued for processing" }

That is not the refund outcome — it means the ticket passed basic validation and entered the queue.

Never read the refund outcome from the processRefund response. Use webhooks or status polling — see Refund lifecycle & statuses.