Copy page

Webhooks

Webhooks notify your own systems automatically when something happens in Order41.

How it works

Create a webhook in your workspace and point it at your own endpoint. When an event happens in Order41, Order41 sends a request to that endpoint, so your tech stack hears about it as it happens.

Before you start

-

Webhooks are included on the Team and Scale plans. See pricing.

-

Only workspace Admins can create and manage webhooks.

-

You need an endpoint on your side that receives the webhook requests, for example https://example.com/webhooks/order41.

Create a webhook

-

Go to Settings → Webhooks and create a new webhook. The Create webhook dialog asks for:

-

URL: the endpoint Order41 sends the webhook requests to.

-

Password: used to sign each webhook payload, so your endpoint can check that a request really comes from Order41. See Security below.

-

Headers: optional headers to send with each request, written as JSON, for example { "key": "value" }.

-

Events: click Add event to choose which events trigger the webhook.

-

Click Create webhook.

Events

Each event combines an object type and an event type. Click Add event and pick one of each, for example Order and Create to hear about every new order. Add as many events to a webhook as you need.

-

Object types: Cart (an order draft), Order, Contact, Product and Drop (a collection).

-

Event types: Create, Update and Delete.

Payload

Each request carries a JSON body with the object's id, the object type, the event type, and a changeset with the object's fields. This is an example for a new order:

{
  "id": 10482,
  "object": "order",
  "event": "create",
  "changeset": {
    "id": 10482,
    "status": true,
    "cancel": false,
    "drop_id": 1207,
    "drop_name": "ACME BRAND - FW26 - REORDER",
    "drop_season": "FW26",
    "buyer_id": 3150,
    "buyer_name": "Acme Store",
    "buyer_email": "",
    "seller_id": 20417,
    "owner_id": 20417,
    "rep_id": null,
    "rep_credential_id": 20533,
    "is_seller": true,
    "is_private": false,
    "qty": 2,
    "currency": "EUR",
    "total_amount": 104,
    "discount_type": "contact",
    "discount_amount": 0,
    "applied_discount_id": null,
    "custom_discount": "",
    "shipping_costs": null,
    "extra_costs": null,
    "shipping_address_id": 6021,
    "invoice_address_id": 6021,
    "invoice_no": "",
    "invoice_date": null,
    "vat": "",
    "comment": "",
    "cart_comment": null,
    "supplier_name": "",
    "range_order_int": "200",
    "range_order_text": "AB",
    "order_tag": 0,
    "rating": null,
    "inform": false,
    "inform_admin": false,
    "urlkey": "x7k2p9qd4mzt1",
    "created_at": "2026-10-20T07:55:40",
    "updated_at": "2026-10-20T07:55:40",
    "deleted_at": null
  }
}

Security

Order41 signs each webhook payload with the password you set for the webhook. Your endpoint can verify the X-BODY-CHECKSUM header using that password.

Good to know

Webhooks can trigger Make scenarios from Order41 events, so you can automate workflows without writing code.

For standard integrations and the public API, see Integrations and API.

Book a demo

Choose a time