> For the complete documentation index, see [llms.txt](https://docs.commercelayer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.commercelayer.io/metrics-api-reference/helpers/analysis/fbt.md).

# FBT

To perform an FBT query send a `POST` request to the `/analysis/fbt` endpoint specifying the item ID(s) in the [filter](#filterable-fields-and-allowed-operators) without any extra query keys:

```json
{
  "filter": {
    "line_items": {
      "item_ids": {
        "in": [
          "...",
          "..."

          // ...

        ]
      }
    }
  },
  "meta": { ... }
}
```

{% hint style="info" %}
Please find more information on how the FBT queries work [here](/metrics/getting-started/analysis/fbt.md).
{% endhint %}

## Filterable fields and allowed operators

Please find below the full list of the fields (and related attributes) you can use in the `filter` object of a FBT query, and the associated allowed values and valid operators.

#### `line_items` field

| Attribute      | Type   | Values                                           |
| -------------- | ------ | ------------------------------------------------ |
| **`item_ids`** | Object | <p>One of:</p><p><code>"in": \["..."]</code></p> |

{% hint style="info" %}
The `item_ids.in` object is a list of SKU or bundle IDs associated as line items to one or more orders and the `in` operator works according to the `AND` logic (i.e. matches *all* of the specified array's values).
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.commercelayer.io/metrics-api-reference/helpers/analysis/fbt.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.