> 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/route-export.md).

# Route Export

{% 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 export supported route data.

This page uses `Route Export` as the primary name.

You may also see this API called `City Pairs API`.

### Main API

* `route/export.do`

### Use this when you need

* Route data exports
* Internal analytics support
* Operational review of route coverage

### Before you call

This API is intended for production route datasets.

Send:

* `routeType`

Use optional filters only when needed:

* `fromCity`
* `fromCountry`
* `toCity`
* `toCountry`
* `airlines`
* `pageNumber`
* `pageSize`

### Route types

* `1`: airline routes
* `2`: Atlas routes

### What the response can include

Returned route records can include:

* airline list
* origin and destination city or country
* direct or connecting indicator
* schedule window
* last update date

`isDirect` is relevant for Atlas route exports.

### Best practice

* use filters to reduce payload size
* paginate large exports instead of requesting everything at once
* refresh local route data based on `updateDate`
* separate airline-route exports from Atlas-route exports in your pipeline

### What to watch

* environment availability should be confirmed before integration
* route data is operational support data, not a booking guarantee
* returned schedules can change over time
* direct and connecting coverage depends on route type and source data

### Full API reference

See the complete endpoint schemas and samples here:

[Route Export](/api-document/api-reference/utility-apis/route-export.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/route-export.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.