Webhooks

A webhook sends a request to a web address of yours whenever something happens in a workspace. Your system hears about a new link straight away, instead of asking the API over and over. Typical uses: post new links to a team chat, add them to a spreadsheet or a CRM, or start your own processing.

Webhooks come with the Team and Business plans: up to 10 endpoints per workspace on Team, 25 on Business. The workspace owner and Admins manage them.

Add an endpoint

1. Open the workspace's Developers page from the menu and scroll to Webhooks.
2. Paste the address that should receive the requests. It must start with https:// and be reachable from the internet.
3. Choose the events it should get, or leave All events ticked to receive every type, including ones we add later.
4. Click Add endpoint. Its signing secret is shown straight away: copy it into your receiver.

The events are: a link is created, a link is edited, a link is deleted, links are bulk-created, a custom domain is verified, and a member joins the workspace. Links made through the API count too.

Check that it works

Click Test on the endpoint. A test event is sent within a few seconds, and the Log opens to show what your endpoint answered. Any answer from 200 to 299 counts as delivered.

The log keeps every request for 30 days: when it was sent, the event, whether it was delivered, and your endpoint's answer. Details shows the exact content we sent and what came back, and Resend sends it again.

Check that a request came from us

Every request is signed with the endpoint's secret, so your receiver can reject anything we did not send. Secret shows it again, and Replace makes a new one, which is used from the next request on. The webhooks reference has ready-to-use code for checking the signature, and the full content of every event.

When your endpoint fails

A request that is not answered with a success within 10 seconds is tried again, several times over about 21 hours. If 20 events in a row fail every try, or nothing has been delivered for three days, we switch the endpoint off and email the workspace owner. Nothing is sent to it while it is off, and events from that time are not sent later. Fix the problem, then click Turn on.

You can also turn an endpoint off yourself while you work on your receiver, and remove it when you no longer need it. If the workspace moves to a plan without webhooks, its endpoints stay listed but nothing is sent to them until the plan includes webhooks again.