Webhooks

Webhooks are in Developers, below the API keys, and send updates to another program. If you do not use automations, you can leave all webhooks off.

New webhook

With New webhook, enter a name, an HTTPS address and the events to send. You can choose events for Subscriptions, Clients, Client projects, Expenses, Time tracking and Documents.

Every delivery carries the X-Reneva-Signature header: an HMAC-SHA256 of the body computed with the secret. Use it to verify the request really comes from Reneva.

Test and log

Use Send test to check the address. At the bottom of Developers, after API log, Webhook log shows the outcome and attempts; it does not show the secret or the data sent.

If the update does not arrive after three attempts, Retry appears in the log. It sends the same update, with the same identifier: whoever receives it can tell it is the same fact.

The retry goes to the address the webhook has now, not to the one of the failed delivery: if you edited it in the meantime, the old delivery reaches the new address. Check the address with Send test before retrying. A webhook that is turned off sends nothing.

Reneva keeps the content of a failed delivery for seven days, then the button disappears. Retrying adds a new row to the log and leaves the failed one as it is.

Webhooks apply to the whole installation. Each update identifies its company by code (data.company). A retry keeps the original event’s company and data, even if you select another company in the panel.