You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Outgoing webhooks: Atom tells other systems when something happens, with a signed POST in the Standard Webhooks format (webhook-id, webhook-timestamp, webhook-signature: v1,<HMAC-SHA256>). An admin subscribes a URL to events with the new route /admin/webhook-create (it returns the whsec_ signing secret once); a project's code calls app_state.func_webhook_send(client_postgres=conn, event="shipment.delivered", data={...}), which queues one delivery per active subscriber as a queue_job row on channel channel_webhook, in the caller's transaction (a rollback sends nothing). With config_webhook_is_active on (off by default), each app worker delivers them (FOR UPDATE SKIP LOCKED, never twice at once), retries a failure after 60 s doubled each time, and keeps it as failed with its error after 8 retries (config_webhook_timeout_sec, config_webhook_retry_max, config_webhook_retry_wait_sec, config_webhook_poll_sec). New table webhook; the URL must be https to a public address, checked at creation and before every delivery; secret joins config_column_read_blocked. Webhooks are listed, paused and deleted through the generic admin routes (docs/webhook.md).