Version

Webhook Events API

A read-only polling endpoint that surfaces the most recent webhook deliveries for a given event type.

A read-only polling endpoint that surfaces the most recent webhook deliveries for a given event type. The envelope is identical to the live webhook POST body, so polling samples and live hook payloads are indistinguishable.

Why it exists. REST Hook integrations (Zapier, Make, n8n) can satisfy the polling fallback contract even when the user has not yet fired a live event. If your team has no deliveries for the requested type, the response is an empty data array; consumers fall back to their static sample in that case.

The endpoint takes webhook-delivery:view-any. A token that still carries the retired webhook-endpoint:manage satisfies it.

Endpoints

GET
curl "https://api.subscriby.net/v1/webhook-events?type=subscription.created&limit=3" \  -H "Authorization: Bearer $SUBSCRIBY_TOKEN"

The most recent deliveries of one event type, newest first, as the envelopes the endpoints received. limit defaults to 3 and is capped at 10; project_id restricts to deliveries whose endpoint is scoped to that project.

api_version is the payload-envelope stamp the dispatcher wrote at delivery time; see versioning. Results are ordered by created_at descending. Only deliveries against endpoints owned by the token's team are returned; other tenants' events are never surfaced.

data is empty when no endpoint in your team is subscribed to the requested event type yet, or when no delivery has fired for that type since the relevant endpoint was created. Zapier, Make, and n8n all fall back to the trigger's static sample in that case, so builders can still author a Zap end-to-end before the first live event flows.

GET
/v1/webhook-events

The token must hold this ability, or the call is refused with 403.

Authorization

bearerToken
AuthorizationBearer <token>

A personal access token minted on the dashboard under Settings, then Tokens, sent as Authorization: Bearer sbt_live_…. The token carries the abilities each endpoint lists under Requires ability and is frozen to one team.

In: header

Query Parameters

type*string

The event name to sample, such as subscription.created; must be a case from the outbound webhook event catalog. An unknown name is refused.

limit?integer

How many recent deliveries to return, 1 to 10.

Default3
project_id?string

Restrict to deliveries whose endpoint is confined to this project.

Formatuuid

Responses

200OK

Array of WebhookEventResource

401Unauthorized

The request carries no bearer token, or one that is revoked, malformed, or minted for another environment (an sbt_test_ token on production).

403Forbidden

The token is valid but does not carry the ability this endpoint requires; error.context.required_ability names the one to grant. An endpoint that also checks who owns a row or which tier the account is on answers FORBIDDEN, TEAM_TIER_REQUIRED or CONNECTOR_TIER_REQUIRED with the same status, and says so in its own description.

404Not found

With reason: missing_team_scope when the token carries no team scope.

422Validation failed

The payload broke a rule, and error.fields maps each offending key to its messages. A refusal from the domain, such as a plan that cannot go on sale or a member who cannot be removed, uses the same code with error.message saying why and no fields. On this endpoint: VALIDATION_FAILED: when type is missing or not an event name from the catalog, limit is outside 1 to 10, or project_id is not a UUID.

429Too many requests

The token has spent its 300 requests a minute or 10,000 an hour; Retry-After says when the next one is accepted.

How is this guide?

Version

On this page

Subscriby is a product
designed by you — for you.
No boardroom full of executives deciding what we ships next. Our roadmap always shaped by you with your feedback.

Share feedback or a request