Webhooks let you receive real-time HTTP notifications whenever something changes in your Take App store. Use them to connect Take App to your own backend, automate workflows, or feed third-party tools — no polling required.
This article covers the general picture. Payload schemas, headers, signature verification code samples, retry behaviour, and the full event catalogue live in the API reference and are kept up to date there:
Webhooks reference: platform.take.app/api-reference/v2/webhooks
Setting up webhooks
- Go to Settings > Integrations and open Webhook
- Click Add endpoint and enter an
https://URL that acceptsPOSTrequests - Select which events this endpoint should subscribe to
- Click Save
Each endpoint has its own signing secret. Copy it anytime from the endpoint's ⋯ → Copy signing secret menu. You can rotate the secret at any time; the old secret stops working immediately.
What you get
- Multiple endpoints — add more than one URL and send the same event to different services.
- Granular event selection — choose exactly which events each endpoint subscribes to.
- Signature verification — every payload is signed with the endpoint's signing secret, so your server can confirm the request genuinely came from Take App.
Available events
- order.created — a new order is placed, or a draft order is activated for the first time
- order.updated — an existing order changes: status, payment, fulfillment, or line items
- product.updated — a product changes: name, price, variants, or options, from any source (admin, API, imports, AI tools)
Event payloads reuse the same Order and Product objects the Merchant API V2 returns, so you only model each shape once.
Handling deliveries safely
Webhooks use at-least-once delivery, so treat them as idempotent: use the X-Take-Delivery-Id header to ignore duplicates. Events are not guaranteed to arrive in order — use the record's updated_at field to discard stale updates. Reject any request whose signature does not match, and any whose timestamp is too old (for example, older than 5 minutes) to defend against replays.
Signature headers and worked verification examples in Node.js and Python are in the webhooks reference.
