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

# Get Inventory Availability

Retrieve current Available-to-Sell (ATS) quantities for all applicable SKUs.

Returns the current Available-to-Sell (ATS) quantity for every applicable SKU. Use it when the consuming system needs a complete inventory availability feed.

`GET /inventory/v1/{identifier}/inventory-availability`

If the request is processed, the <mark style="color:$success;">`200`</mark> - **OK** response is returned.

### Purpose

Use the GET endpoint to retrieve the complete availability set without maintaining a SKU list.

* No request body is required.
* No SKU list is required.

{% tabs %}
{% tab title="Retrieve inventory availability " %}
{% @code-walkthrough/try-it specLoaded="" specEps="" method="GET" path="/inventory/v1/{identifier}/inventory-availability" baseUrl="<https://api.sandbox.esw.com>" title="" defaults="{"path":{"identifier":""},"query":{},"headers":{"Content-Type":"application/json"}}" mode="open" %}
{% endtab %}
{% endtabs %}

{% hint style="info" %}
To retrieve only specific SKUs, or to supply a delivery country, use [Get Inventory Availability for SKUs](/inventory/inventory-api/api-methods/get-inventory-availability-for-skus.md).
{% endhint %}

### Request

| Item             | Value                                               |
| ---------------- | --------------------------------------------------- |
| Method           | `GET`                                               |
| Path             | `/inventory/v1/{identifier}/inventory-availability` |
| Sandbox base URL | `https://api.sandbox.esw.com`                       |

#### Headers

<table><thead><tr><th width="256">Header</th><th width="113">Type</th><th width="89">Req.</th><th>Notes</th></tr></thead><tbody><tr><td><code>Authorization</code></td><td>string</td><td><mark style="color:$danger;"><code>req</code></mark></td><td>Bearer JWT: <code>Bearer {access_token}</code>. See <a href="/inventory/inventory-api/authentication.md">Authentication</a>.</td></tr></tbody></table>

#### Path parameters

<table><thead><tr><th width="256">Parameter</th><th width="113">Type</th><th width="89">Req.</th><th>Notes</th></tr></thead><tbody><tr><td><code>identifier</code></td><td>string</td><td><mark style="color:$danger;"><code>req</code></mark></td><td>The applicable retailer identifier.</td></tr></tbody></table>

{% code expandable="true" %}

```bash
curl --request GET 'https://api.sandbox.esw.com/inventory/v1/{identifier}/inventory-availability' \
  --header 'Authorization: Bearer {access_token}'
```

{% endcode %}

### Response

<mark style="color:$success;">`200`</mark> OK. The response is an array containing the current ATS quantity for each applicable SKU.

{% code expandable="true" %}

```json
[
  {
    "sku": "SKU123",
    "quantity": 57
  },
  {
    "sku": "SKU456",
    "quantity": 12
  }
]
```

{% endcode %}

<details open>

<summary>Response fields</summary>

<table><thead><tr><th width="256">Field</th><th width="113">Type</th><th>Notes</th></tr></thead><tbody><tr><td><code>sku</code></td><td>string</td><td>The SKU for which the available-to-sell quantity is provided.</td></tr><tr><td><code>quantity</code></td><td>integer</td><td>The current ATS quantity. Always zero or greater, never negative.</td></tr></tbody></table>

</details>

### Status codes

| Status | Description                                          |
| ------ | ---------------------------------------------------- |
| `200`  | Request processed successfully                       |
| `400`  | Request is invalid                                   |
| `401`  | Request is unauthorized                              |
| `403`  | Request is forbidden                                 |
| `404`  | Required ESW fulfillment configuration was not found |
| `409`  | ESW fulfillment configuration conflict               |
| `500`  | Internal server error                                |

See [Response Codes](/inventory/inventory-api/response-codes.md) for error structures and recommended actions.

{% hint style="info" %}
The quantity is ATS: inventory available for new demand after inventory controls and existing commitments, not physical On Hand stock. See [Available-to-Sell (ATS)](/inventory/inventory-api/concepts/available-to-sell-ats.md).
{% endhint %}

{% 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 %}


---

# 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/api-methods/get-inventory-availability.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.