Create compensation
createCompensations — create one or more Requests
createCompensations — create one or more RequestsSubmits one or more new Requests in a single call. Each item returns with its own uuid so you can follow up with request using that value while processing continues in the background.
Input: inputs: [CompensationInput!]! — must not be empty.
| Field | Required | Description |
|---|---|---|
ticketNumber | Yes | Ticket number: exactly 13 digits |
pnr | No | Reservation code: 6 letters or digits (stored as given on the Request, normalized to upper case) |
waiverCode | No | Optional waiver reference for the compensation flow |
requestDate | No | Optional time (ISO-8601) for when the compensation was requested in your system |
Your account: which organization the Request belongs to is taken from your signed-in session.
New Requests receive a new uuid and an initial runStatus (for example PROCESSING) while work proceeds.
Authentication: required — see How to authenticate.
Example:
mutation StartCompensations {
createCompensations(
inputs: [
{
ticketNumber: "1234567890123"
pnr: "ABCDEF"
waiverCode: "WAIVER01"
requestDate: "2026-03-30T12:00:00.000Z"
}
]
) {
id
uuid
ticketNumber
runStatus
}
}Typical headers:
Authorization: Bearer <your access token>Related queries
requests— search and page through Requests with filters. Details: REQUESTS_QUERY.md.reservation/reservations— reservation (PNR) information linked to Requests.
If something is wrong with the input or the service, the response follows normal GraphQL errors with a message your integration can show or log.
Updated 30 days ago