For the complete documentation index, see llms.txt. This page is also available as Markdown.

Void

Atlas API void reference for checking void eligibility, submitting void requests, and tracking their status.

💬 Need help? If you're stuck, ask Eva in the Help Center for instant diagnostics.

Ask Eva

Use this section for the dedicated void lifecycle.

Start here when you need to:

  • check whether an order is still voidable

  • submit a void request with the latest voidOfferId

  • track void processing and outcome

Need the workflow guide first?

Use Void workflow.

FAQ

What is the standard Atlas API void flow?

The standard flow is voidQuotation.dovoid.doqueryVoidOrders.do.

Request quotation first.

Then submit the void with the latest voidOfferId.

After submission, query status with orderNo.

Add voidCode when you want a specific void case.

Will Atlas reject a void request after the deadline?

Yes.

If the returned same-day void deadline has already passed, void.do fails in real time.

Typical error message:

  • Void deadline exceeded. This ticket can no longer be voided

Does Atlas support partial-pax void?

No.

Atlas accepts full-order void only.

Do not submit void for only some passengers.

Is voidQuotation.do still required when the service fee is fixed?

Yes.

Call voidQuotation.do before every void.do request.

When should I use Void instead of Refund?

Use Void when the order is still inside the airline void window.

Use Refund when the void window has passed or the case needs the refund flow.

Current VOID coverage

Atlas VOID supports 23 airlines across four regions as of July 2026.

Coverage is airline-, route-, and account-specific.

Americas

  • AS

  • DM

  • F9

  • G4

  • PB

  • SY

  • TS

  • Y4

Europe

  • A3

  • D8

  • EI

  • DY

  • N0

  • OA

  • VF

  • Z0

Japan

  • ZG — US routes only

Korea

  • 7C

  • BX

  • LJ

  • RS

  • TW

  • ZE

Recent additions as of July 2026:

  • TS

  • Y4

  • EI

  • VF

If the booking is outside this scope, Atlas can return 843.

What this section covers

  • Request void quotations

  • Submit void requests

  • Query void status and results

Typical flow

1

Void Quotation

Check whether the order is voidable.

Read the latest amount, method, and voidOfferId.

2

Submit Void

Submit the void request with the latest quotation result.

Keep the returned voidCode for follow-up.

3

Query Void Status

Track progress until the void is completed, rejected, or otherwise closed.

Use orderNo as the main query key.

Add voidCode when you want to narrow the result to one void case.

What should you confirm before void submission?

Confirm:

  • the original orderNo is correct

  • the order is still inside the airline void window

  • the returned same-day deadline has not passed yet

  • the latest voidOfferId is used

  • the case should go through Void, not Refund

Void handling is usually stricter than refund handling.

Window expiry can make the order non-voidable even if refund is still possible.

If the deadline already passed, Atlas rejects the void request immediately.

Key behavior

  • Void uses dedicated endpoints

  • quotation should run before submission

  • voidOfferId is used for submission

  • orderNo is used for void query

  • voidCode can narrow query follow-up to one void case

Main APIs

  • voidQuotation.do

  • void.do

  • queryVoidOrders.do

Request model

Use the dedicated void flow with these inputs:

  • voidQuotation.do: orderNo

  • void.do: orderNo + voidOfferId

  • queryVoidOrders.do: orderNo + optional voidCode

Endpoint notes

voidQuotation.do

Use quotation to get the latest void eligibility and amount.

Expect the response to answer:

  • whether the order is voidable

  • which voidMethod applies

  • which voidOfferId to use next

Important fields to read first:

  • isVoidable

  • voidOfferId

  • expectedConfirmationDate

  • expectedRefundDate

  • voidWindow.sameDayDeadlineTime

  • voidWindow.sameDayTimezone

void.do

Submit the void with the latest voidOfferId.

Keep the returned voidCode.

Use that code for all later status follow-up.

Do not skip quotation, even when the service fee is fixed.

If the returned same-day deadline already passed, Atlas rejects the request in real time.

queryVoidOrders.do

Use query to track the void after submission.

Pass orderNo as the main query key.

Add voidCode when you want one specific void case under that order.

Atlas usually returns a processing decision within about five minutes.

Final completion or rejection can still take longer.

This is a typical operating result, not a contractual SLA.

Important fields to read first:

  • voidCode

  • voidStatus

  • cancelReason

  • actualRefundAmount when available

Status handling

The main outcome states to watch are:

  • processing

  • refunded or fulfillment done

  • rejected

If the void is rejected, check cancelReason first.

If the void window expired, move the case to the refund flow when applicable.

Integration notes

Use the latest quotation result before submission.

Do not reuse an older voidOfferId.

Treat the void window as strict.

If the order is no longer voidable, do not keep retrying the void path.

Webhook option

Atlas can also send order.void to your registered webhook URL.

Use it after void.do for near-real-time status updates.

Webhook is the recommended way to follow progress changes after submission.

Read these fields first:

  • data.orderNo

  • data.voidCode

  • data.voidStatus

  • data.message

No extra webhook registration is required.

Use the same URL registered through updateWebhookURL.do.

Use queryVoidOrders.do when you need final reconciliation.

Read Void Notification.

Void Quotation

post
Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json
Accept-EncodingstringRequiredDefault: gzipExample: gzip
x-atlas-client-idstringRequiredDefault: <YOUR_CLIENT_ID>Example: <YOUR_CLIENT_ID>
x-atlas-client-secretstringRequiredDefault: <YOUR_CLIENT_SECRET>Example: <YOUR_CLIENT_SECRET>
Body
orderNostringRequired

Atlas original order number. You can choose to request either orderNo or both airlinePNR and carrier.

Example: TESTA20260610091023287
Responses
200Success
application/json
statusintegerRequired

Status code 0 : Success 801:Order not found for void. Check the original main ticket order number. 803:Void already submitted for this passenger or segment. Query void status instead. 805:voidOfferId expired. Call refundQuotation.do again for a fresh ID, then resubmit. 808:This ticket is non-voidable per airline policy. 810:Invalid request parameters 814:Void submission already in progress. Wait before retrying. 815:Ticket not found. Verify ticket number and order number. 816:Void already submitted for this order. Query void status instead of resubmitting. 817:Void already submitted for this order. Query void status instead of resubmitting. 818:Void already submitted for this order. Query void status instead of resubmitting. 820:Ticket already used — cannot void a flown segment. 822:Void deadline exceeded. This ticket can no longer be voided. 824:Wrong orderNumber: use the main ticket order, not the ancillary order number. 841:Void not support the payment method. Please contact the airline directly for resolution. 843:Atlas does not currently support VOID service for the airline or route of this booking.

msgstring · nullableRequired

Error message The ‘msg’ element is for description of the results. Please do not use this field to check the success or failure of the request. Only use the ‘status’ code to check the result.

fastConfirmationinteger · enumRequired

Fast confirmation depends on whether the airline supports auto fulfillment. 0 for False, 1 for True.

Possible values:
expectedConfirmationDatestringRequired

Expected date of getting airline void confirmation. The format is yyyyMMdd.

expectedRefundDatestringRequired

Expected date of getting refund. The format is yyyyMMdd.

voidOfferIdstringRequired

Void offer id for this quotation which can be used for the coming Void call.

voidMethodstring · enumRequired

Void method: CashBackToOriginalPayment or Voucher. CashBackToOriginalPayment: Refund cash back to the original form of payment. Voucher: Refund in the form of a voucher.

Possible values:
orderNostringRequired

Original order number

isVoidablebooleanRequired

True : Voidable False: Non-Voidable true or false

post/voidQuotation.do
200Success

Make a Void

post

Void quotation function should be called in prior of this call

Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json
Accept-EncodingstringRequiredDefault: gzipExample: gzip
x-atlas-client-idstringRequiredDefault: <YOUR_CLIENT_ID>Example: <YOUR_CLIENT_ID>
x-atlas-client-secretstringRequiredDefault: <YOUR_CLIENT_SECRET>Example: <YOUR_CLIENT_SECRET>
Body
orderNostringRequired

Atlas original order number. You can choose to request either orderNo or both airlinePNR and carrier.

voidOfferIdstringRequired

Get this from the void quotation response.

Responses
200Success
application/json
statusintegerRequired

Status code 0 : Success, 801:Order not found for void. Check the original main ticket order number. 803:Void already submitted for this passenger or segment. Query void status instead. 805:voidOfferId expired. Call refundQuotation.do again for a fresh ID, then resubmit. 808:This ticket is non-voidable per airline policy. 810:Invalid request parameters 814:Void submission already in progress. Wait before retrying. 815:Ticket not found. Verify ticket number and order number. 816:Void already submitted for this order. Query void status instead of resubmitting. 817:Void already submitted for this order. Query void status instead of resubmitting. 818:Void already submitted for this order. Query void status instead of resubmitting. 820:Ticket already used — cannot void a flown segment. 822:Void deadline exceeded. This ticket can no longer be voided. 824:Wrong orderNumber: use the main ticket order, not the ancillary order number. 841:Void not support the payment method. Please contact the airline directly for resolution. 843:Atlas does not currently support VOID service for the airline or route of this booking.

msgstring · nullableRequired

Error message The ‘msg’ element is for description of the results. Please do not use this field to check the success or failure of the request. Only use the ‘status’ code to check the result.

fastConfirmationintegerRequired

Fast confirmation depends on whether the airline supports auto fulfillment. 0 for False, 1 for True.

expectedConfirmationDatestringRequired

Expected date of getting airline void confirmation. The format is yyyyMMdd.

expectedRefundDatestringRequired

Expected date of getting refund. The format is yyyyMMdd.

voidOfferIdstringRequired

Void offer id for this quotation which can be used for the coming void call.

voidMethodstringRequired

Voidmethod: CashBackToOriginalPayment or Voucher. CashBackToOriginalPayment: Refund cash back to the original form of payment. Voucher: Refund in the form of a voucher.

orderNostringRequired

Original order number

isVoidablebooleanRequired

True : Voidable False: Non-Voidable true or false

voidStatusintegerRequired

The present status of the void. The options are: 0: Atlas Processing 1: Airline Processing (Submitted to airline by Atlas) 2: Refunded 3: Airline Refunding 4: Rejected 5: Fullfillment Done 6: Withdrew If the ticket is paid by deposit: the status can be 0,1,2,3,4 If the ticket is paid by VCC pass through: the status can be 0,1,4,5,6 Withdrew is only in the refund claim

voidCodestringRequired

Void order number generated for this void request

cancelReasonstringRequired

The reason why the void was cancelled.

post/void.do
200Success

Query Void Status

post

No preceding function needs to be carried out.

Header parameters
AcceptstringRequiredExample: application/json
Content-TypestringRequiredExample: application/json
Accept-EncodingstringRequiredDefault: gzipExample: gzip
x-atlas-client-idstringRequiredDefault: <YOUR_CLIENT_ID>Example: <YOUR_CLIENT_ID>
x-atlas-client-secretstringRequiredDefault: <YOUR_CLIENT_SECRET>Example: <YOUR_CLIENT_SECRET>
Body
orderNostringRequired

Atlas original order number.

voidCodestringOptional

The code of the void transaction received in the void.do response.

Responses
200Success
application/json

Void order query response

statusintegerRequired

API status code. 0 : Success 801: No voidable orders found. Please check the original main ticket order number. 803: Passenger or segment has already submitted a void request. Please check the void status. 805: voidOfferId has expired. Please call refundQuotation.do again to get a new ID and resubmit. 808: This ticket cannot be voided according to airline policy. 810: Invalid request parameters. 814: Void submission is already in process, please try again later. 815: Ticket not found. Please verify the ticket number and order number. 816: This order has already submitted a void request. Please check the void status, do not resubmit. 817: This order has already submitted a void request. Please check the void status, do not resubmit. 818: This order has already submitted a void request. Please check the void status, do not resubmit. 820: Ticket already used - cannot void flown segments. 822: Void deadline has passed. This ticket can no longer be voided. 824: Wrong order number: Please use the main ticket order number, not the ancillary service order number. 841: Void is not supported for this payment method. Please contact the airline directly for processing. 843: Atlas currently does not support void service for this airline or route.

msgstring · nullableRequired

Error message

post/queryVoidOrders.do
200Success

Last updated

Was this helpful?