Integrations
Webhooks
Push events to your systems: subscriptions, the event catalog, signing secrets, test deliveries, and the delivery log.
Subscriptions
Settings → Webhooks pushes events to your endpoints as they happen. A subscription pairs a destination URL — public HTTPS only — with the event types it wants:
stock.changed · item.created · item.updated · movement.created ·
po.received · count.completed · low-stock · export.completed
Creating a subscription reveals its signing secret once — store it like a password; rotate secret later without recreating the subscription.
Deliveries
Delivery is at-least-once with retries and a dead-letter state: consumers must be idempotent (dedupe on the event id) and should verify the HMAC signature on the raw body before trusting anything — the receiver-side details live in the developer webhook guide.
Test delivery sends a sample event to the endpoint, and the delivery log shows every attempt with status and response; replay re-sends a delivery after you've fixed the receiving end. When your endpoint has an outage, the log plus replay is your recovery story.
Webhooks require the integrations capability and webhook permissions; managing subscriptions is audited. For pull-style integration instead of push, the API's events feed serves the same events on a cursor.