asset.images.updated
Images were added, replaced or removed for a product. Changes made close together arrive as one event, about a minute later. data: added and removed: image ids. Read the asset again for the images themselves.
CharpstAR-Event*stringCharpstAR-Delivery*stringThe delivery id; the same on every retry.
uuidCharpstAR-Signature*stringt=,v1=<hex HMAC SHA-256 of t + '.' + raw body, keyed with your whsec_ secret>
User-Agent*stringapplication/json- body
id*stringThe delivery id; the same as the CharpstAR-Delivery header and the same on every retry.
uuidtype*stringoccurredAt*stringWhen it happened on our side.
date-timeclient*The company the key belongs to.
article*|The article number the event is about, or null when the event is not about one product.
data*Any 2xx within 10 seconds means handled. Anything else is retried.
{ "id": "9a8b7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d", "type": "asset.images.updated", "occurredAt": "2026-10-20T09:31:00.000Z", "client": { "id": "e2b7c1d4-5a6f-4b8c-9d0e-1f2a3b4c5d6e", "name": "Your Company" }, "article": "CH-1001", "data": { "added": [ "8d2f4c1a-packshot" ], "removed": [] }}{ "CharpstAR-Event": "asset.images.updated", "CharpstAR-Delivery": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "CharpstAR-Signature": "string", "User-Agent": "CharpstAR-Webhooks/1"}asset.approved Webhook
A model is approved. We hold the event until the files are live (up to 30 minutes), so it usually arrives with status delivered and every link filled in. This is the one to act on. data: The full asset, as in GET /api/v1/assets/{article}. If the files were not live in time, only articleId and status approved; status.changed follows once it is delivered.
job.succeeded Webhook
A job finished and its outputs are on the product. data: The job as it finished, as in GET /api/v1/jobs/{jobId}, outputs included.