List a webhook’s deliveries (legacy path)
List a webhook’s deliveries (legacy path)
The v1 path of the delivery log, retained as an alias. It is served by the same handler as
GET /api/webhooks/{webhookId}/deliveries and returns the same response (same query parameters,
same { data, meta: { next_cursor } } shape). Use /deliveries.
Access
- Required scope:
readorwrite. Any workspace role can call it. - Rate limit: General API — 120 requests/min per workspace on Starter or with no active plan, 200 on Growth, 300 on Business, 600 on Enterprise. See Rate limits.
- Plan: Available on every plan and also without an active subscription. See Billing and usage.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.
Path parameters
UUID of the outbound webhook endpoint, returned as id by GET /api/webhooks. It must belong to the authenticated workspace; an id from another workspace, an unknown id or a value that is not a UUID answers 404.
Query parameters
meta.next_cursor from the previous page.
Response
Same as GET /api/webhooks/{webhookId}/deliveries.

