> For the complete documentation index, see [llms.txt](https://docs.eventication.com/event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eventication.com/event/general/integrations/catalyst/stock-articles.md).

# Stock articles

{% hint style="info" %}
This endpoint requires the **stock\_items** access to be enabled in the Catalyst integration settings.
{% endhint %}

#### <mark style="color:$success;">GET</mark> `/catalyst/stock_items`

Returns the individual [stock articles](https://docs.eventication.com/event/stock/inventory-categories/types/articles.md) for the event. A stock item is one physical unit of a stock type (e.g. a specific tent with a serial number).

* URL: `https://api.eventication.com/catalyst/stock_items?page=1`
* Page size: **200 objects per request**
* Fields per item:
  * `id`
  * `name` — name or description of this specific item
  * `code` — optional barcode / serial number
  * `stock_type_id` — references an item from [stock\_types](https://docs.eventication.com/event/general/integrations/catalyst/stock-types.md)
  * `current_state` — current physical condition: `good`, `damaged`, `theft`, `dirty`, or `lost`
  * `amount` — quantity (decimal)
  * `unit` — one of `articles`, `kg`, `lb`, `m`, `l`

Example item:

```json
{
  "id": 101,
  "name": "4-person tent #12",
  "code": "T0012",
  "stock_type_id": 10,
  "current_state": "good",
  "amount": "1.0",
  "unit": "articles"
}
```

Response shape:

```json
{
  "data": [
    {
      "id": 101,
      "name": "4-person tent #12",
      "code": "T0012",
      "stock_type_id": 10,
      "current_state": "good",
      "amount": "1.0",
      "unit": "articles"
    },
    ...
  ],
  "meta": {
    "page": 1,
    "per_page": 200,
    "next_page": 2,
    "prev_page": null
  }
}
```


---

# 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://docs.eventication.com/event/general/integrations/catalyst/stock-articles.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.
