← All webhook events

Subscribe to service_order.assigned

A service order is assigned to a partner CA / paralegal for fulfilment.

When does service_order.assigned fire?

Admin clicks Assign on /admin/service-orders or Clairvoyis auto-matches based on specialisation + rating.

What developers build with it

  • Provider notification
  • SLA timer start
  • Workspace provisioning in provider portal

Sample payload

The full envelope (with HMAC-SHA256 signature, delivery UUID and headers) is documented on the webhooks hub page. Below is the per-event data block for service_order.assigned:

{
    "order_id": 1421,
    "order_number": "SO/2026-27/00091",
    "ngo_id": 7,
    "status": "assigned",
    "assigned_provider_id": 5
}

Subscribe to this event

From your NGO dashboard, head to System · Webhooks · Add new. Paste your HTTPS endpoint, copy the signing secret, tick service_order.assigned in the events list, save. The first matching event fires within seconds. Verify the X-Donateazy-Signature header on every request.

// PHP example - drop into your webhook receiver
$raw = file_get_contents('php://input');
$expected = hash_hmac('sha256', $raw, $WEBHOOK_SECRET);
if (! hash_equals($expected, $_SERVER['HTTP_X_DONATEAZY_SIGNATURE'] ?? '')) {
    http_response_code(401); exit;
}

$payload = json_decode($raw, true);
if ($payload['event'] !== 'service_order.assigned') {
    http_response_code(202); exit; // not for this handler
}

// $payload['data'] is the block documented above.
handleServiceOrderAssigned($payload['data'], $payload['id']);
http_response_code(200);

Build your first integration in 10 minutes.

Webhooks ship on Pro and above. Full API reference, signature verification and idempotency on the hub.

Read the full reference See pricing
Chat with us