Events
An event is a single incoming HTTP request that an endpoint received and stored. It's the canonical record of what a provider sent — Webhookr persists the full payload and headers so the event can be inspected and replayed.
Model
| Field | Description |
|---|---|
id | Unique identifier. |
endpointId | The endpoint that received it. |
method | HTTP method of the request. |
payload | The full request body (JSON). |
headers | All request headers. |
payloadSize | Size of the body in bytes. |
headerCount | Number of headers. |
sourceIp | IP address the request came from. |
userAgent | The sender's User-Agent. |
contentType | Request content type. |
receivedAt | When the event was received. |
lastReplayedAt | When the event was last replayed, if ever. |
createdAt | When the record was created. |
Lifecycle
- A provider posts to the endpoint's ingest URL.
- Webhookr validates the endpoint (exists and is active) and stores the event, returning
202 Accepted. - For each enabled destination, Webhookr creates a delivery and attempts to forward the event.
Storing and delivering are separate steps: an event is always stored first, even if it has no destinations or a delivery later fails.
Inspecting & replaying
Browse and open events in the dashboard under Events. From an event you can replay it to its destinations.