Skip to navigation

Ticket documents

Resend the confirmation emails and download the tickets
View as Markdown

Once a booking is ticketed, you can resend the confirmation emails and download the ticket PDFs. These run on the notification and ticket services, not the OTA endpoint, so they use their own URLs and do not take a local-name header. They still authenticate with your x-api-key or JWT.

You do not have to build download URLs by hand. Once a booking with named passengers is ticketed, the API hands you one link per ticket PDF in tpaextensions.links:

  • in the ticketing response, under each ticketItemInfo[].passengerName
  • in OTA_ReadRQ and OTA_AirBookModifyRQ responses for a paid booking, under each ticketing[].tpaExtensions
"links": [
{
"href": "https://api.sar.worldticket.cloud/sms-gateway-service/tickets/confirmation/N6G2NW/download/passenger-segment?ticketNumber=3333330058951&couponNumber=1",
"rel": "downloadTicket",
"segmentRPH": "1",
"travelerRPH": "1"
}
]

rel is always downloadTicket. segmentRPH and travelerRPH say which segment and traveler the PDF belongs to, so you can match it to the itinerary. Call href as given. The older urls field next to it, a space-separated string, is deprecated; read links.

Resend the ticket email

POST /sms-gateway-service/notifications/email sends the ticket confirmation again. Give the record locator, the recipients, and the passengers whose tickets to include. A successful call returns 204 No Content. It works only for a confirmed booking that is still active and has its tickets issued.

curl -X POST https://api.sar.worldticket.cloud/sms-gateway-service/notifications/email \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"emails": ["traveler@example.com"],
"ccEmails": [],
"bccEmails": [],
"recordLocator": "N6G2NW",
"passengers": [
{ "firstName": "BARAA", "lastName": "BUKHARI" },
{ "firstName": "SARA", "lastName": "BUKHARI" }
]
}'

Resend the cancellation email

POST /sms-gateway-service/notifications/cancellation-email resends the cancellation notice. Give the record locator and the recipients. It returns 204 No Content. The cancel operation already sends this email on its own; use this only when you need to send it again.

List segments to limit the email to specific cancelled segments. Leave it out and the email covers every cancelled segment in the booking.

curl -X POST https://api.sar.worldticket.cloud/sms-gateway-service/notifications/cancellation-email \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"emails": ["traveler@example.com"],
"ccEmails": [],
"bccEmails": [],
"recordLocator": "N6G2NW",
"segments": [
{ "flightDesignator": "HHR0141", "departure": "JXD", "arrival": "MKX", "departureDate": "2026-05-20" }
]
}'

Download all tickets

GET /sms-gateway-service/tickets/confirmation/{rloc}/download returns the booking’s tickets as a ZIP of PDFs. Put the record locator in the path.

curl "https://api.sar.worldticket.cloud/sms-gateway-service/tickets/confirmation/N6G2NW/download" \
-H "x-api-key: YOUR_API_KEY" \
--output tickets.zip

An optional mode query parameter picks what goes in the archive:

modeWhat you get
fullEvery ticket in the booking. This is the default.
deltaOnly the tickets that changed since the last full set.
legacyAn older name for delta. It behaves the same.

Any other value returns 400 Bad Request.

curl "https://api.sar.worldticket.cloud/sms-gateway-service/tickets/confirmation/N6G2NW/download?mode=delta" \
-H "x-api-key: YOUR_API_KEY" \
--output tickets_delta.zip

Download one ticket

GET /sms-gateway-service/tickets/confirmation/{bookingReference}/download/passenger-segment returns a single ticket PDF. Identify it with the ticket number and coupon number, which you get from the ticketing response or from ticketing[] on a read booking. This works for group bookings too, where you may not know the passenger names.

curl "https://api.sar.worldticket.cloud/sms-gateway-service/tickets/confirmation/N6G2NW/download/passenger-segment?ticketNumber=3333330058951&couponNumber=1" \
-H "x-api-key: YOUR_API_KEY" \
--output ticket.pdf

The older form of this call, which identified the ticket with firstName, lastName, departure, and arrival, is deprecated and will be removed. Move to ticketNumber and couponNumber.

For the full parameters, see the GO7 download_tickets page.