> For the complete documentation index, see [llms.txt](https://developer.esw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.esw.com/order-api/order-api/order-api.md).
# Overview
Overview of the Order API for creating, managing, fulfilling, cancelling, replacing, and tracking cross-border orders and transactions
The Order Transaction API is the central order management layer in the ESW cross-border commerce platform. It handles the full lifecycle of orders — from initial creation through fulfilment, cancellation, line-item operations, appeasements, replacements, allocation, and financial transaction search.
It provides a suite of functionalities for managing order-related activities. It allows for retrieving order transactions, canceling entire orders or specific line items, issuing replacements or appeasements, and updating shopper contact details.
The Order API is asynchronous, which means that when ESW receives the API request, the ESW system validates it and returns a response indicating whether your request is accepted or not. If your request is accepted and subsequently processed, the ESW system triggers success or failure event notifications to let you know that your request has now been actioned. Note that these event notifications are sent only if you are subscribed to receive notifications from ESW.
#### What this API does
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://developer.esw.com/order-api/order-api/order-api.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
