Apply Content Change Group
POST/api/content-sync/group-apply
Applies every open change in one bucket in the background, without listing ids. The bucket is described by the same filters used to list it, so a bucket of several thousand listings needs no enumeration by the caller. Send the filters in the QUERY STRING — filters in the request body are ignored, which would silently widen the apply. The apply must be scoped by at least one of filter[field], filter[field_group], or filter[integration_instance_ids]; an unscoped call returns 422. High-impact fields such as product name are rejected with 422 and must be applied one listing at a time. Very large buckets are applied in passes: listings_queued below listings_total means the call should be repeated to continue. Follow progress with the returned tracked_job_log_id. Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Unprocessable Entity
Response Headers
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.