← All webhook events

Subscribe to campaign.completed

A campaign reaches its goal amount OR its end date passes. The reason field disambiguates: goal_reached vs end_date_passed.

When does campaign.completed fire?

Scheduled task evaluates campaign state at the goal-reached threshold or at end_date. Includes final raised_amount and donor_count.

What developers build with it

• → Trigger campaign thank-you broadcast email
• → Generate impact-report draft via ORIS campaign-writer
• → Update website with success metrics
• → Push success story to social-media queue
• → Auto-archive the donate button on the public campaign URL

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 campaign.completed:

{
    "campaign_id": 18,
    "ngo_id": 7,
    "title": "Monsoon Relief 2026",
    "reason": "goal_reached",
    "goal_amount": 1000000,
    "raised_amount": 1024500,
    "donor_count": 187,
    "completed_at": "2026-08-12T14:32:11+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 campaign.completed 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'] !== 'campaign.completed') {
    http_response_code(202); exit; // not for this handler
}

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

Often paired with

All 20 webhook events