Skip to main content
POST
Commit a batch; the sync engine drains it
Committing hands the batch to the sync engine, which writes it into your canonical data. The interactive playground is turned off here so a docs page can never trigger a real ingest. Copy the request and run it against your own workspace.

Authorizations

Authorization
string
header
required

Elastly API key. Scopes: erp (price serving), connector (ingest + write-backs), storefront.

Path Parameters

batchId
string<uuid>
required

Response

The enqueued sync job.

jobId
string
required