EMD Refund & Void API Reference
|
Put |
emds/{EMDNumber} Base path: Pre-production https://api.pp.travelport.net/11/air/ Production https://api.travelport.net/11/air/ Travelport has updated all JSON API authentication and authorization endpoints. Previous endpoints are scheduled for deprecation 5 Dec 2025 for pre-production and 30 Jan 2026 for production. You must migrate to the endpoints above before those dates or transactions in those environments will fail. See Endpoint Migration for details.
|
Related Content: Ancillary and EMD Guide, EMD Display API Reference
Void an EMD to cancel it. You can also use EMD void with the GDS exchange APIs to refund an EMD back to the original FOP. See the Exchange, Refund, and Void Guide.
EMD Void not supported for NDC.
Request
As part of the request requirements, also see Authentication and Common Air Headers.
Query Parameters
None.
Request Body
|
Object |
Description |
Required/Optional |
|---|---|---|
|
EMDQueryUpdateEMD |
Empty top level object. |
Required |
|
Supported values:
|
Required |
Response
|
Object |
Description |
|---|---|
|
EMDListResponse |
Empty top level object. |
|
Result |
Returns messages about transaction. Key value pair:
|
Example Request
The message payload sends a blank EMDQueryUpdateEMD object.
{
"EMDQueryUpdateEMD" : {
}
}
Example Response
The EMD void returns the following response when successful.
{
"EMDListResponse": {
"Result": {
"status": "Complete"
}
}
}
When a voided EMD is retrieved using the EMD Display request, the EMDSegment/Status is Void, per the example below.
...
"EMDSegment": [
{
"EMDDescription": {
"code": "A",
"subCode": "0B5",
"codeContext": "IATA",
"value": "Air transportation"
},
"Amount": {
"CurrencyCode": {
"value": "AUD"
},
"Total": 26.36
},
"Status": "Void",
"PresentTo": "VA/VIRGIN AUSTRALIA INTERNATIONAL",
"PresentAt": "MEL/MELBOURNE"
}
],
...