> 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-for-skus.md).

# Get Inventory Availability for SKUs

Retrieve Available-to-Sell (ATS) quantities for a specified list of SKUs, optionally for a shopper's delivery country.

Returns the current Available-to-Sell (ATS) quantity for a specified list of SKUs. Optionally supply the shopper's delivery country so the quantity reflects the inventory applicable to that market.

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

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

### Purpose

Use the POST endpoint when the consuming system needs ATS quantities for specific SKUs, for example the items in a basket or on a product listing. To retrieve every applicable SKU, use [Get Inventory Availability](/inventory/inventory-api/api-methods/get-inventory-availability.md).

{% tabs %}
{% tab title="Retrieve inventory availability  for SKUs" %}
{% @code-walkthrough/try-it specLoaded="" specEps="" method="POST" path="/inventory/v1/{identifier}/inventory-availability" baseUrl="<https://api.sandbox.esw.com>" title="Get available-to-sell quantity for a list of SKUs" defaults="{"path":{"identifier":""},"query":{},"headers":{"Content-Type":"application/json"}}" mode="open" %}
{% endtab %}
{% endtabs %}

### Request

| Item             | Value                                               |
| ---------------- | --------------------------------------------------- |
| Method           | `POST`                                              |
| 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><tr><td><code>Content-Type</code></td><td>string</td><td><mark style="color:$danger;"><code>req</code></mark></td><td><code>application/json</code></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>

#### Request body

The body is a stock availability request.

<details open>

<summary>Fields</summary>

<table><thead><tr><th width="256">Field</th><th width="113">Type</th><th width="89">Req.</th><th>Constraints &#x26; notes</th></tr></thead><tbody><tr><td><code>skus</code></td><td>array of strings</td><td><mark style="color:$danger;"><code>req</code></mark></td><td>The list of SKUs for which ATS quantities should be returned. Must be a valid SKU list.</td></tr><tr><td><code>deliveryCountryIso</code></td><td>string</td><td><mark style="color:$warning;"><code>opt</code></mark></td><td>The shopper's two-character ISO 3166-1 alpha-2 delivery country code. See <a href="/inventory/inventory-api/concepts/delivery-country-availability.md">Delivery-Country Availability</a>.</td></tr></tbody></table>

</details>

{% code expandable="true" %}

```bash
curl --request POST 'https://api.sandbox.esw.com/inventory/v1/{identifier}/inventory-availability' \
  --header 'Authorization: Bearer {access_token}' \
  --header 'Content-Type: application/json' \
  --data '{
    "deliveryCountryIso": "FR",
    "skus": [
      "SKU123",
      "SKU456"
    ]
  }'
```

{% endcode %}

### Response

<mark style="color:$success;">`200`</mark> OK. The response is an array containing the ATS quantity for each requested SKU. When a delivery country is supplied, the quantity is aggregated across the fulfillment centres applicable to that country.

{% code expandable="true" %}

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

{% 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 available-to-sell quantity for the SKU. 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="warning" %}
Ensure the request contains a valid SKU list and validate `deliveryCountryIso` when you supply it.
{% 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-for-skus.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.