> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frontic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Trigger Fetch List

Trigger Frontic to pull a **list** of records from the external system. Useful for webhook-style triggers like "this category changed — re-pull everything in it" where Frontic fans out the fetch through its connector.

Two requirements:

* The Data Feed must be configured with method **trigger** or **polling** (not **ingest**).
* The integration's connector must support listing fetches (`FetchListAwareInterface` in source). Not every integration implements this — calling `/fetch-list` against a connector that doesn't support it returns an error.

## Path Parameters

<ParamField path="integration-id" type="string" required>
  Your integration identifier. Found in the admin app under integration settings.
</ParamField>

<ParamField path="feed-id" type="string" required>
  The unique identifier for your data feed.
</ParamField>

## Request Body

The body is a trigger signal — it identifies which list to fetch. The exact shape depends on your integration's connector; typical patterns include a parent identifier (e.g. a category ID) or a query filter.

<ParamField body="id" type="string">
  Identifier for the list scope (e.g. a category ID). Specific connectors may accept additional fields.
</ParamField>

## Response

<ResponseField name="correlation-id" type="string" required>
  Unique identifier to track the fetch through the processing pipeline.
</ResponseField>

<RequestExample>
  ```json Trigger Body theme={"theme":"css-variables"}
  {
    "id": "category-shoes"
  }
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={"theme":"css-variables"}
  {
    "correlation-id": "66g2i0h1-6e06-8i52-c5e9-77g64b113b1b"
  }
  ```
</ResponseExample>