> For the complete documentation index, see [llms.txt](https://resources.atriptech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://resources.atriptech.com/api-document/readme/post-booking-overview/post-booking-operations.md).

# Post-booking Operations

{% hint style="info" %}
💬 **Need help?** If you're stuck, ask Eva on ATRIP for instant diagnostics.

<a href="https://www.atriptech.com/" class="button primary" data-icon="comments">Ask Eva</a>
{% endhint %}

Use this section for operational actions after a booking is ticketed or needs follow-up.

Start here when you need to:

* handle a ticketed order that needs operational action
* choose between refund, maintenance, ancillary, or PNR claim workflows
* route a post-ticketing case to the right detailed guide

### FAQ

#### What belongs in post-booking operations?

Use this section for refund actions, void actions, ticket maintenance, post-ticketing ancillaries, and PNR claim or extraction work after the original booking flow.

#### Which page should we open first for a post-ticketing case?

Open the page that matches the task.

Use **Refunds** for refund flow, [**Void**](/api-document/readme/post-booking-overview/post-booking-operations/void.md) for the dedicated void flow, **Order Maintenance** for intervention tasks, **Post-ticketing Ancillaries** for extra seat or baggage handling, and **PNR Claim & Extraction** for claim or extraction cases.

### Pages in this section

* [Order Maintenance](/api-document/readme/post-booking-overview/post-booking-operations/order-maintenance.md)
* [Refunds](/api-document/readme/post-booking-overview/post-booking-operations/refunds.md)
* [Void](/api-document/readme/post-booking-overview/post-booking-operations/void.md)
* [Post-ticketing Ancillaries](/api-document/readme/post-booking-overview/post-booking-operations/post-ticketing-ancillaries.md)
* [PNR Claim & Extraction](/api-document/readme/post-booking-overview/post-booking-operations/pnr-claim-and-extraction.md)

### Use this when you need

* Handle refunds after ticketing
* Handle void requests inside the airline void window
* Regenerate or stop ticketing operations
* Add ancillaries to issued tickets
* Extract PNRs or manage claim flows

### What comes next?

If the current order state is still unclear, check [Query Order](/api-document/readme/booking-overview/query-order.md) first.

Then continue with the matching post-booking workflow page.

### Related pages

* [Post-booking Overview](/api-document/readme/post-booking-overview.md)
* [Webhook Overview](/api-document/readme/webhook-overview.md)
* [Utility API Overview](/api-document/readme/utility-api-overview.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://resources.atriptech.com/api-document/readme/post-booking-overview/post-booking-operations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.