...
There's currently no limit on webhooks and they can be installed per deployment from an individual users account using the webhooks control panel. The control panel can be accessed from the administration configuration page → api → webhooks.
Access
Only pro users and up can utilise webhooks. This doesn't mean other users cannot register them on behalf but webhooks will only fire on objects the owner of the object has view access to. For example, If Alice registers to receive notifications whenever a task assignee changes. She will not receive notifications for any tasks she cannot view from within Accelo.
Limitations
We do not limit the amount of webhooks per deployment or user but we do enforce a 10 second timeout rule. If your trigger url takes more than 10 seconds to respond to webhook delivery, we will cancel the request. If this occurs too many times, we will delete your webhook subscription automatically.
...
| Event ID | Description |
|---|---|
| assign_task | Any time a task assignee changes. This includes going from assigned to unassigned. |
| create_quote | Any time a new quote is created. |
| create_request | Any time a new request is created. |
| update_request_status | Any time a request status changes. |
| create_invoice_pdf | Any time a PDF resource is generated. |
Payloads
Each event will bundle together a payload containing the details of what happens and a resource url pointing you where to go for more fields of the object affected.
...
| Header | Description |
|---|---|
| X-Accelo-Event | ID of the even event that triggered the delivery. For example, "assign_task" |
| X-Hub-Signature | HMAC hex digest of the payload using your configured subscriptions secret. |
...
Manually dispatch a given subscription synchronously. Alike Unlike triggering, this will only execute the current subscription so other subscriptions of the even event will not be affected. As it's synchronously you will get the HTTP status of the webhook result.
...