> 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/utility-api-overview/email-query.md).

# Email 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 Atlas email records linked to orders.

This page uses `Email Query` as the primary name.

You may also see this API called `Email List`.

### Main API

* `queryMail.do`

### Use this when you need

* Investigate airline emails for an order
* Check whether Atlas received a notification email
* Review email categories before support follow-up
* Retrieve a short-lived email view link

### Before you call

Send at least one query condition:

* `orderNo`
* `emailReceivingDateStart` and `emailReceivingDateEnd`
* `createTimeStart` and `createTimeEnd`

Keep each time range within `1 month`.

### Main filters

* `orderNo` for exact order lookup
* receiving time range for airline email arrival time
* creation time range for Atlas record creation time
* `emailCategories` for category filtering
* `pageIndex` and `pageSize` for pagination

### Supported email categories

Common values include:

* `Travel Itinerary`
* `Schedule Change`
* `Payment Due`
* `Payment Success`
* `Receipt`
* `Trip Reminder`
* `PNR Cancellation Success`
* `Advertisement`
* `Duplicated Schedule Change`
* `Verification`
* `Unaccounted Cancellation`
* `Promo code`

### What to watch

* Time fields use `UTC+08:00`
* `emailReceivingDate` is when Atlas received the airline email
* `createTime` is when Atlas created the record
* `emailLink` is valid for only `10 minutes`
* Atlas classifies emails, but category accuracy is not guaranteed

### Best practice

* use `orderNo` first when you already know the booking
* use receiving time for airline-notification investigations
* use creation time when reconciling Atlas records
* store email metadata if you need a longer audit trail
* do not rely on `emailLink` for long-term access

### Full API reference

See the complete endpoint schemas and samples here:

[Email Query](/api-document/api-reference/utility-apis/email-query.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/utility-api-overview/email-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.