Overview
Subscriptions monitor blockchain activity at an address and deliver matching on-chain events to your webhook URL. Use the /subscriptions endpoints to manage subscriptions; use /subscriptions/events to list, inspect, and retry the delivery events those subscriptions emit.
- List subscriptionsGET/subscriptions
- Create subscriptionPOST/subscriptions
- Get subscriptionGET/subscriptions/:id
- Update subscriptionPATCH/subscriptions/:id
- Delete subscriptionDELETE/subscriptions/:id
- Rotate signing secretPOST/subscriptions/:id/rotate-secret
- List delivery eventsGET/subscriptions/events
- Get delivery eventGET/subscriptions/events/:id
- Retry delivery eventPOST/subscriptions/events/:id/retry
List Subscriptions
Use Case
Returns a paginated list of subscriptions for the organization, filterable by chain, network, and status.
Query Parameters
Opaque cursor — pass next_cursor from a prior response to fetch the next page.
Opaque cursor for reverse pagination.
Page size.
Filter by blockchain (e.g., ethereum, tron).
Filter by network (e.g., mainnet, testnet).
Filter by subscription status.
Create Subscription
Use Case
Creates an address subscription to monitor blockchain activity. Matching events are POSTed to webhook_url.
Request Body
On-chain address to monitor.
Blockchain the address lives on (e.g., ethereum, tron).
HTTPS endpoint that will receive delivery events.
Network within the chain (e.g., mainnet, testnet).
Specific event type to monitor (e.g., transfer). Defaults to all event types.
Free-form label for your own bookkeeping.
Arbitrary key-value JSON returned back on every subscription read.
Create Subscription Response
data is a single SubscriptionResponse — the same object shape used in each entry of List Subscriptions Response. Refer there for the per-field explanations.
Get Subscription
Use Case
Returns a single subscription by ID.
Get Subscription Response
data is a single SubscriptionResponse — the same object shape used in each entry of List Subscriptions Response. Refer there for the per-field explanations.
Update Subscription
Use Case
Partially updates a subscription. Only event_type and webhook_url can be changed.
Request Body
Updated event type to monitor.
Updated webhook endpoint.
Delete Subscription
Use Case
Soft-deletes the subscription and detaches it from the upstream provider. Subsequent on-chain events will not be delivered.
Response: 204 No Content — empty body.
Rotate Signing Secret
Use Case
Generates a new HMAC signing secret for this subscription's webhook URL. The new secret is returned once — store it before the response closes.
The plaintext signing_secret is returned only on this response. Subsequent reads only expose a masked form. Use it to verify the signature header on every delivery.
Rotate Signing Secret Response
Resource type identifier. Always signing_secret.
The new HMAC signing secret. Returned only on this response — store it before the response closes.
List Delivery Events
Use Case
Returns a paginated list of on-chain delivery events across all subscriptions, newest first. Filterable by delivery status or subscription ID.
Query Parameters
Opaque cursor — pass next_cursor from a prior response to fetch the next page.
Opaque cursor for reverse pagination.
Page size.
Filter by delivery status: pending, delivered, or failed.
Narrow to a single subscription.
Get Delivery Event
Use Case
Returns a single delivery event by ID. The event must belong to the caller's organization.
Get Delivery Event Response
data is a single EventResponse — the same object shape used in each entry of List Delivery Events Response. Refer there for the per-field explanations.
Retry Delivery Event
Use Case
Re-queues a specific delivery for another attempt. Useful for delivering events that previously failed.