Travel Agency Email API Reference
POST |
ticket/travelagency/reservationworkbench/{workbenchID}/travelagency/{travelagencyID}/addemail For {workbenchID} send the workbench identifier returned in ReservationResponse/Identifer/value in the workbench create response. For {travelagencyID} send the identifier returned in TravelAgency/id in the Workbench Create and Workbench Retrieve responses. Base path: Pre-production https://api.pp.travelport.com/11/air/ Production https://api.travelport.com/11/air/ |
Put |
ticket/travelagency/reservationworkbench/{workbenchID}/travelagency/{travelagencyID}/updateemail See the POST request above for variables and the base path. |
DEL |
ticket/travelagency/reservationworkbench/{workbenchID}/travelagency/{travelagencyID}/deleteemai/l{emailID} For {emailID} send the identifier returned in TravelAgency/Email/id in the Workbench Create and Workbench Retrieve responses. See the POST request above for other variables and the base path. |
Related Content:Booking Guide, Travel Agency Details API Reference
The Travel Agency Email API supports POST, PUT, and DEL requests to add, modify, or delete a travel agency email address to the booking A confirmed reservation with the carrier. A held booking is a reservation that has not yet been ticketed. The terms booking and reservation are interchangeable. in the current workbench. All requests must be sent as part of a workbench session, either during the initial booking workflow or a post-commit
Refers to the state of a booking after the booking is created, which happens after the initial booking workbench is commited and the reservation locator code issued. workbench for an existing booking, and followed by a workbench commit.
For adding only, you can instead use the Travel Agency Details API to add all travel agency details in a single request using one payload.
The reservation retrieve for a booking returns any travel agency details associated with that booking.
Request
Also see Authorization and Common Headers.
Query Parameters
None.
Request Body
Use the following request for the update operation. The delete request does not have a message body.
Note the different endpoints for each operation per above.

Object |
Description |
Required/Optional |
---|---|---|
TravelAgencyQueryTravelAgencyEmailWrapper |
Top level object. |
Required |
TravelAgencyQueryTravelAgencyEmail |
Top level object. |
Required |
|
Top level object for email address. |
Required |
|
String. Max length 128. Email address. |
Required |
Response
The response returns the travel agency identifier and the details sent in the request.

Object |
Description |
---|---|
TravelAgencyResponse |
Top level object. Includes TravelAgency object. |
TravelAgency |
Corporate code value. Key value pair:
|
Identifier |
System-generated identifier for the travel agency; use this in subsequent update and delete request:
|
|
Id for the address sent in the add or update request. Key value pair:
|
Example Request
Use the following request to modify any part of a travel agency email address.
The delete response returns a No Content message.

{
"TravelAgencyQueryTravelAgencyEmailWrapper": {
"TravelAgencyQueryTravelAgencyEmail": {
"Email": {
"@type": "Email",
"id": "email_1",
"value": "sindar.singh@none.com"
}
}
}
}
Example Response
The following response is returned for the update travel agency email request.
The delete response returns a 204 No Content message.

{
"TravelAgencyResponse": {
"TravelAgency": {
"@type": "TravelAgencyDetail",
"id": "travelAgency_1",
"Identifier": {
"value": "328a3a99-dd30-486f-9653-37619bdbdbe5",
"authority": "Travelport"
},
"Email": [
{
"id": "email_1"
}
]
}
}
}