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

Trigger Frontic to pull a single record from the external system. Used by webhook-style integrations where the source system signals that a record changed, and Frontic uses its connector logic to fetch the current state from the source — the request body itself isn't the data.

The Data Feed must be configured with method **trigger** or **polling**. Calling `/fetch` against an ingest-method feed 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 record to fetch but isn't the record itself. The exact shape depends on your integration's connector implementation; typically a source ID is enough.

<ParamField body="id" type="string">
  Source ID of the record to fetch from the external system. Specific connectors may accept additional identifying 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": "product-123"
  }
  ```
</RequestExample>

<ResponseExample>
  ```json 200 OK theme={"theme":"css-variables"}
  {
    "correlation-id": "55f1h9g0-5d95-7h41-b4d8-66f53a002a0a"
  }
  ```
</ResponseExample>