Webhooks let another system react the moment something finishes in DepreciationPro, instead of polling to find out. This is for firms with an integration. If nobody at your firm is building against the API, you do not need this page.
Go to Settings → Webhooks.
The four events
Event | Fires when |
| A depreciation recompute finishes. |
| A depreciation recompute fails. |
| An async export job reaches completed. |
| An async export job fails permanently. |
The computation events fire on explicit recompute triggers only. That means a call to POST /api/v1/returns/{id}/depreciation/recompute, or a write-initiated recompute flow. Reading the depreciation endpoints does not emit an event, so polling GET /api/v1/returns/{id}/depreciation or /form-4562 will never produce one.
Registering an endpoint
Click Register webhook. Endpoints must be HTTPS, and you can have a maximum of 5 active per firm.
You will see the signing secret exactly once. Copy it when it is shown and store it wherever your integration keeps its secrets. There is no way to see it again, so a lost secret means registering the endpoint afresh.
Use the secret to verify that a delivery genuinely came from DepreciationPro before acting on it.
Who can do this
Managing webhooks is a Technical Admin permission. Managers do not have it. See User roles, and what each one can do.