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

# Overview

Inventory API and the two Available-to-Sell (ATS) endpoints that return SKU-level inventory availability.

The Inventory API allows authorized retailer storefronts and commerce platform integrations to retrieve current Available-to-Sell (ATS) inventory at SKU level. ATS is the quantity currently available for new demand after applicable inventory controls and existing commitments have been considered.

#### Integration Purpose

Use the Inventory API to keep storefront and platform availability aligned with ESW, either as a complete feed of every applicable SKU or as a lookup for specific SKUs and a shopper's delivery country.

#### What this API Does

| Capability                              | Method and path                                          | What it returns                                                                  |
| --------------------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------------- |
| **Get Inventory Availability**          | `GET /inventory/v1/{identifier}/inventory-availability`  | ATS quantities for all applicable SKUs. No request body or SKU list is required. |
| **Get Inventory Availability for SKUs** | `POST /inventory/v1/{identifier}/inventory-availability` | ATS quantities for a specified list of SKUs, optionally for a delivery country.  |

{% hint style="success" %}
Use `GET` for the complete inventory availability set. Use `POST` when availability is needed for specific SKUs.
{% endhint %}

#### Things to know

* Both endpoints return ATS, not physical On Hand stock. See [Available-to-Sell (ATS)](/inventory/inventory-api/concepts/available-to-sell-ats.md).
* `quantity` is an integer that is always zero or greater.
* When a delivery country is supplied on POST, ESW determines the applicable inventory. See [Delivery-Country Availability](/inventory/inventory-api/concepts/delivery-country-availability.md).
* Both endpoints require Bearer authentication. See [Authentication](/inventory/inventory-api/authentication.md).

{% hint style="danger" %}
A failed API request must not be interpreted as zero inventory. Treat a quantity of `0` as a valid zero-ATS position only when it is returned in a successful response.
{% endhint %}

#### Where to go next

| Page                                                                           | Use it to                                                 |
| ------------------------------------------------------------------------------ | --------------------------------------------------------- |
| [Authentication](/inventory/inventory-api/authentication.md)                   | Get an access token and authenticate requests             |
| [Concepts](/inventory/inventory-api/concepts.md)                               | Understand ATS, delivery-country behavior and GET vs POST |
| [API Methods](/inventory/inventory-api/api-methods.md)                         | See request and response details for each endpoint        |
| [Use Cases](/inventory/inventory-api/use-cases.md)                             | Follow end-to-end scenarios                               |
| [Response Codes](/inventory/inventory-api/response-codes.md)                   | Handle each HTTP status correctly                         |
| [First Successful Requests](/inventory/resources/first-successful-requests.md) | Make your first calls                                     |


---

# 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/overview.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.