> 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/webhook-overview/incident-query.md).

# Incident Query

{% 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 page to search incident records when webhook delivery or event state needs confirmation.

Start here when you need to:

* reconcile missed or unclear webhook events
* search incidents by order, airline, passenger, or time range
* investigate schedule-change or cancellation history

### FAQ

#### When should I use Incident Query?

Use Incident Query when webhook delivery, incident history, or event confirmation still needs deeper reconciliation.

#### Which filters should I start with?

Start with `orderNo` for one affected booking.

Add `eventType`, airline, or time range filters when the incident set is broader.

### Main API

* `event/getPageList.do`

### Use this when you need

* Reconcile missed webhook events
* Filter incidents by order, passenger, or airline
* Review event confirmation status
* Investigate schedule change or cancellation history

### Common query patterns

#### Find incidents for one order

Use:

* `orderNo`
* `pageSize`

#### Find schedule changes for one airline

Use:

* `eventType`
* `airline`
* `eventTimeStart`
* `eventTimeEnd`
* `pageSize`

#### Find unresolved incidents

Use:

* `eventStatus`
* `pageSize`

### Common filters

* `eventId`
* `orderNo`
* `eventType`
* `pnr`
* `paxName`
* `paxEmail`
* `airline`
* `eventStatus`
* `eventTimeStart`
* `eventTimeEnd`
* `pageIndex`
* `pageSize`

### Required field

* `pageSize`

### Response highlights

* `records`
* `pageIndex`
* `pageSize`
* `total`
* Event status and confirmation fields

### Tips

* always send `pageSize`
* start with `orderNo` when debugging one affected booking
* add time ranges when querying broad incident sets
* use this together with webhook payload logs and order query results

### What comes next?

Use the query result together with [Query Order](/api-document/readme/booking-overview/query-order.md) and [Incident Notification](/api-document/readme/webhook-overview/incident-notification.md) to confirm the final operational state.

### Full API reference

See endpoint-level details here:

* [Webhook Registration & Incidents](/api-document/api-reference/webhook-and-incident-apis/webhook-registration-and-incidents.md)

### Related pages

* [Incident Notification](/api-document/readme/webhook-overview/incident-notification.md)
* [Schedule Change Notification](/api-document/readme/webhook-overview/schedule-change-notification.md)
* [Query Order](/api-document/readme/booking-overview/query-order.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/webhook-overview/incident-query.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.