Skip to main content
POST /api/v1/webhooks accepts every event key in the tables on this page. Event names are stable subscription identifiers; marketplace-specific topic names never appear in the events array.

Product and catalog

A single product mutation can emit product.updated and a more specific price or inventory event. Each delivery has its own eventId; consume every event type you subscribe to and deduplicate each one independently. See Product webhooks for payload fields and examples.

Account statements

Account statement changes and sync lifecycle events are also supported. See Account statement webhooks for the complete event list, payload semantics, and AOP/Project trigger support.

Orders

Order events use the versioned 2026-08-01 provider-neutral contract. See Order webhooks.

Returns

Return events use the versioned 2026-08-29 PII-free contract. See Return webhooks.

Settlements

Settlement events are independent of order lifecycle events because marketplace finance commonly arrives later and can be adjusted. See Settlement webhooks.

Looks

There is no look.updated subscription event today. See Look webhooks.

Reviews

An unchanged resync does not emit another event. A status change is review.status.changed only, not also review.updated. There is no review.replied event. Buyer names are omitted. See Review webhooks.

Test deliveries

The Webhooks settings page can send webhook.test to one subscription. It uses the same signature headers, but it is not a subscription event and is rejected if included in POST /api/v1/webhooks.

Not yet subscribable

These resource families are planned but are not accepted subscription keys and are not emitted as developer webhooks today: Do not subscribe to guessed keys such as payout.created or fulfillment.updated. OmniCommerce returns 400 for any event outside the catalog.