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

# API Methods

Reference for the two Inventory API methods: GET and POST Inventory Availability.

The Inventory API has two methods on the same path: `/inventory/v1/{identifier}/inventory-availability`. Both require Bearer authentication and return an array of `sku` and `quantity`.

| Method | Name                                                                                                               | Use it when                                                                |
| ------ | ------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------- |
| `GET`  | [Get Inventory Availability](/inventory/inventory-api/api-methods/get-inventory-availability.md)                   | You need the complete availability set for all applicable SKUs             |
| `POST` | [Get Inventory Availability for SKUs](/inventory/inventory-api/api-methods/get-inventory-availability-for-skus.md) | You need availability for specific SKUs, optionally for a delivery country |

For schema-level detail, see the Inventory API reference.


---

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