Guides

Cancelling

Cancel a whole booking in one call
View as Markdown

You cancel a whole booking in a single call. The API cancels the full booking and emails the confirmation on its own.

Cancellation flow: send the cancel, booking is cancelled, confirmation email
Cancellations always succeed

All cancellation requests are approved, and the associated tickets are cancelled within the cancellationTimeLimit period. The refund amount, however, differs depending on the agreed policies with SAR.

Send the cancel

Call OTA_CancelRQ with the W1 record locator in uniqueID (type 14) and set cancelType to Commit.

1{
2  "version": "2.001",
3  "pos": {
4    "source": [
5      {
6        "isoCurrency": "SAR",
7        "requestorID": { "id": "AGENT001", "name": "Sample Travel", "type": "5" },
8        "bookingChannel": { "type": "OTA" }
9      }
10    ]
11  },
12  "uniqueID": [{ "id": "N6G2NW", "type": "14" }],
13  "cancelType": "Commit"
14}

What comes back

The response returns status CANCELLED for the same locator.

1{
2  "success": {},
3  "uniqueID": [{ "type": "14", "id": "N6G2NW" }],
4  "status": "CANCELLED",
5  "timeStamp": "2026-05-01T09:45:27.963Z",
6  "version": 2.001,
7  "retransmissionIndicator": false
8}

The railway sends the cancellation email to the CTC contact automatically. You do not send it yourself.

This covers full cancellation, which is what production supports. For the complete request and response, see the GO7 cancel_booking page.

How is the refund amount determined?

The refund amount is calculated based on the fare and cancellation policies agreed with SAR. This includes the refund amount, the refund percentage, and any other refund-related terms defined in that agreement.

You are responsible for refunding your clients: The refunded amount is credited to your wallet. Returning that amount to your clients is your responsibility, not SAR’s.

Refunds are credited to your wallet

SAR credits the refund to your wallet. You are responsible for passing it on to your clients.