> 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/resources/first-successful-requests.md).

# First Successful Requests

Make your first successful Inventory API requests: get a token, check selected SKUs for a delivery country, and retrieve the full availability set.

Use these steps to confirm your integration can reach the Inventory API. Replace the placeholders with the values provided during integration setup.

{% stepper %}
{% step %}

#### Get an access token

Request a token as described in [Authentication](/inventory/inventory-api/authentication.md) and keep the `access_token` value.
{% endstep %}

{% step %}

#### Check availability for specific SKUs

Call the POST endpoint with one or two SKUs and, optionally, a delivery country.

```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"]
  }'
```

A successful call returns `200` with an array of `sku` and `quantity`.
{% endstep %}

{% step %}

#### Retrieve the full availability set

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

{% endstep %}

{% step %}

#### Check the result

* `200`: the request was processed. A `quantity` of `0` is a valid zero-ATS position.
* `401` or `403`: check the token and permissions.
* `404` or `409`: contact ESW so the fulfillment configuration can be reviewed.
  {% endstep %}
  {% endstepper %}

Next, follow the [Tutorials](/inventory/resources/tutorials.md) for complete walkthroughs.


---

# 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/resources/first-successful-requests.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.