Business Pro plan workspaces support up to 30,000 webhook events per billing period. Check your plan limits before setting up high-volume automations.
Supported events
You can subscribe a webhook to any combination of the following events:| Category | Events |
|---|---|
| Service | Created, Updated, Deleted |
| Order | Created, Updated, Deleted |
| Task | Created, Assigned, Completed, Updated |
| Invoice | Status changed |
| Client / User | New client added, Client/user deleted |
| Proposal | Sent, Received, Accepted, Rejected |
| Ticket | Created, Assigned, Status changed |
| Payment | Received, Failed |
| Service Package | Created, Updated, Deleted |
Create a webhook
Authenticate your token
Click the Management button to authenticate your webhook token. This token is used to sign outgoing payloads so you can verify they originated from AgencyHandy.
Enter the endpoint URL
In the Endpoint URL field, enter the URL of the external system that should receive the webhook data. This must be a publicly accessible POST endpoint.
Select the content type
Choose JSON as the content type. AgencyHandy sends all webhook payloads as
application/json.Select webhook events
Choose every event that should trigger this webhook. You can select events from multiple categories — for example, Order: Created and Invoice: Status changed can both point to the same endpoint.
Activate the webhook
Toggle the Active radio button. When active, AgencyHandy delivers payloads for all selected events to your endpoint in real time.
Test a webhook
After creating a webhook, send a test payload to confirm your endpoint is reachable and processing data correctly.Select a test event
Choose a sample event from the list of events configured on this webhook (e.g., Order: Created).
Authenticate webhook payloads
Every outgoing webhook request from AgencyHandy includes a signature header that your endpoint can use to verify the payload is genuine and hasn’t been tampered with.Signature header
Verify a webhook signature
Send the following request to confirm a payload is authentic:The ID of the webhook that received the event. Find this on the webhook detail page in AgencyHandy.
The value of the
x-ah-sig header from the incoming webhook request.The webhook secret shown on the webhook detail page in AgencyHandy.
The raw JSON body received from AgencyHandy’s webhook request.
SUCCESS when the signature is valid. FAILED when verification fails (HTTP 403).Success (200)
Failure (403)
Important notes
- Your endpoint URL must be a publicly accessible HTTPS POST URL.
- If your endpoint is temporarily unavailable, check the webhook’s history panel in AgencyHandy — you can redeliver any past event directly from there.
- Regularly monitor webhook activity to detect failed deliveries or unauthorized access attempts.
- Webhooks that fail repeatedly may be paused by AgencyHandy — review delivery logs to catch issues early.

