Roll Back Content Change
POST/api/product-listings/:productListing/content-changes/:contentChange/rollback
Restore the catalog value that an applied change replaced. Nothing is deleted: the original entry is marked rolled_back and a new audit entry records the restore, so the history stays complete.
Only a change that actually reached the catalog can be rolled back (applied, auto-applied, or a previous rollback) — anything else returns 409. The change must belong to the listing in the path, otherwise 404. The listing's content baseline moves with the restore, so the next sync does not read the rollback as fresh drift. Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 409
- 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.
Not Found
Response Headers
Conflict
Response Headers
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
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.