Ticket documents
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.
Resend the ticket email
POST /sms-gateway-service/notifications/email sends the ticket confirmation again. Give the record locator and the recipients. A successful call returns 204 No Content.
Resend the cancellation email
POST /sms-gateway-service/notifications/cancellation-email resends the cancellation notice. Give the record locator, the recipients, and the cancelled segments. 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.
Download all tickets
GET /sms-gateway-service/tickets/confirmation/{rloc}/download returns every ticket for the booking as a ZIP of PDFs. Put the record locator in the path.
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.
For the full parameters, including the mode option on the download, see the GO7 download_tickets page.

