> 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/inventory/inventory-api.md).

# Inventory API

- [Overview](https://developer.esw.com/inventory/inventory-api/overview.md): Inventory API and the two Available-to-Sell (ATS) endpoints that return SKU-level inventory availability.
- [Authentication](https://developer.esw.com/inventory/inventory-api/authentication.md): How to authenticate Inventory API requests with a Bearer JWT and how to request an access token.
- [Concepts](https://developer.esw.com/inventory/inventory-api/concepts.md): Core concepts for the Inventory API: Available-to-Sell quantities, delivery-country availability, and choosing between GET and POST.
- [Available-to-Sell (ATS)](https://developer.esw.com/inventory/inventory-api/concepts/available-to-sell-ats.md): What Available-to-Sell (ATS) means, which inventory controls affect it, and how it differs from physical On Hand stock.
- [Delivery-Country Availability](https://developer.esw.com/inventory/inventory-api/concepts/delivery-country-availability.md): How supplying a delivery country on the POST endpoint determines the inventory applicable to a shopper's market.
- [Decision Tables](https://developer.esw.com/inventory/inventory-api/concepts/decision-tables.md): Decision tables for choosing between the GET and POST Inventory Availability endpoints.
- [API Methods](https://developer.esw.com/inventory/inventory-api/api-methods.md): Reference for the two Inventory API methods: GET and POST Inventory Availability.
- [Get Inventory Availability](https://developer.esw.com/inventory/inventory-api/api-methods/get-inventory-availability.md): Retrieve current Available-to-Sell (ATS) quantities for all applicable SKUs.
- [Get Inventory Availability for SKUs](https://developer.esw.com/inventory/inventory-api/api-methods/get-inventory-availability-for-skus.md): Retrieve Available-to-Sell (ATS) quantities for a specified list of SKUs, optionally for a shopper's delivery country.
- [Use Cases](https://developer.esw.com/inventory/inventory-api/use-cases.md): Four end-to-end scenarios showing how to use the Inventory API to keep availability in sync, check selected SKUs for a delivery market, and handle failures safely.
- [Response Codes](https://developer.esw.com/inventory/inventory-api/response-codes.md): HTTP response codes returned by the Inventory API, the error body schemas, and how to handle each response.
- [FAQs](https://developer.esw.com/inventory/inventory-api/faqs.md): Answers to common questions about the Inventory API, Available-to-Sell quantities, delivery-country behavior, and error handling.


---

# 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/inventory/inventory-api.md?ask=<question>&goal=<user_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.
