{
"id": "category-shoes"
}
{
"correlation-id": "66g2i0h1-6e06-8i52-c5e9-77g64b113b1b"
}
Ingest API
Trigger Fetch List
POST
/
ingest
/
{feed-token}
/
fetch-list
{
"id": "category-shoes"
}
{
"correlation-id": "66g2i0h1-6e06-8i52-c5e9-77g64b113b1b"
}
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 (
FetchListAwareInterfacein source). Not every integration implements this - a/fetch-listcall to a connector that doesn’t support it is still accepted with a200, but nothing is fetched.
Path Parameters
string
required
Your integration identifier. Found in the admin app under integration settings.
string
required
Your Data Feed’s token, which is the value in the feed’s Ingest URL. The feed also has a separate
id; the token is the one that belongs in the URL. Find it in the admin app under your feed settings.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.string
Identifier for the list scope (e.g. a category ID). Specific connectors may accept additional fields.
Response
string
required
Unique identifier to track the fetch through the processing pipeline.
{
"id": "category-shoes"
}
{
"correlation-id": "66g2i0h1-6e06-8i52-c5e9-77g64b113b1b"
}