A list of endpoints, with a button to add one and a log of each endpoint's deliveries.
The list
Columns: the URL (with its description), the events it receives (an "All events" badge when none were chosen), status (Active or Disabled) and actions: view the delivery log, and delete if you can manage. Filter by URL or description text and by status; the filters are kept in the address.
Add an endpoint
Press Add endpoint (needs Manage and the plan feature).
- URL (up to 2048 characters).
- Secret: you type it, 16 to 256 characters, in a plain visible box. Use a long random value and store it where your receiving system can read it. It is used to sign every request and is not shown again; there is no way to recover it or have one generated.
- Description (optional, up to 255).
- Events: search the list of platform events, or type a custom name; up to 500, removable as chips. Leave it empty for all events.
There is no name field and no setting for headers.
What you cannot do
There is no edit, no pause, no test button, no redeliver and no secret change. To change a URL, the events or the secret, delete the endpoint and add a new one; deleting removes its delivery log too. To stop deliveries, delete the endpoint.
The delivery log
Open it from a row. It lists the latest 50 attempts: event, attempt (#1, #2, #3), status (the HTTP code, or "err" if there was no response) and time. There is no error text and no filter.
An attempt whose address is blocked as internal, or whose endpoint was deleted while queued, writes no row. If your system says it received nothing and the log is empty, check the address and that the plan still includes webhooks.
Checking a delivery
A delivery is made with up to three attempts over about 6 minutes. See Webhooks for the signature and what counts as success.