Subscribe to csr.application.decided

When does csr.application.decided fire?

A reviewer or the configured approval workflow reaches a final decision on a submitted application.

What developers build with it

• → Notify the applicant NGO of the outcome
• → Kick off partner onboarding when approved
• → Update funding-call pipeline dashboards
• → Archive rejected applications in your CRM

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 csr.application.decided:

{
    "application_id": 57,
    "call_id": 9,
    "applicant_ngo_id": 44,
    "status": "approved",
    "requested_amount": 400000,
    "decided_at": "2026-07-10T16:40:00+05:30"
}

Subscribe to this event

From your NGO dashboard, head to System · Webhooks · Add new. Paste your HTTPS endpoint, copy the signing secret, tick csr.application.decided 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 = 'sha256=' . 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'] !== 'csr.application.decided') {
    http_response_code(202); exit; // not for this handler
}

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

Often paired with

All 27 webhook events