The Ingest API powers data ingestion in your Frontstack project. Pre-built connectors automatically use this API to process updates from your data pipeline into your Data Feeds.For scenarios where you need more control or when a pre-built connector isn’t available, you can directly interact with the Ingest API through a Custom Integration.
All requests to the Ingest API need to be authenticated. You will receive the API key during Frontstack onboarding.Provide this API key as the Authorization HTTP header in your Ingest API requests.
The “Upsert” endpoint receives a POST request with a JSON object in its body and returns (with status code 200) a JSON object containing a correlation ID, e.g. like this:
This correlation ID is used in Frontstack’s processing to track a particular data change. If you have questions about the processing of a data change, you should provide this correlation ID to us.It replaces the previous record version with the same source ID with the new one.
The “Patch” endpoint receives a POST request with a JSON object in its body and returns (with status code 200) a JSON object containing a correlation ID, e.g. like this:Single record
The “Delete” endpoint receives a POST request with a JSON object in its body and returns (with status code 200) a JSON object containing a correlation ID, like the Upsert endpoint does as well.The request body must contain a id field, which is the source ID of the record to be deleted. See this example:
Copy
// DELETE{"id": "my-product-123"}
You may alternatively provide a JSON list containing one or multiple source IDs in the request body, like this: