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 Subscriptions

Use Case

Returns a paginated list of subscriptions for the organization, filterable by chain, network, and status.

List Subscriptions

Query Parameters
1
starting_afterstring

Opaque cursor — pass `next_cursor` from a prior response to fetch the next page.

2
ending_beforestring

Opaque cursor for reverse pagination.

3
limitinteger

Page size.

4
chainstring

Filter by blockchain (e.g., `ethereum`, `tron`).

5
networkstring

Filter by network (e.g., `mainnet`, `testnet`).

6
statusstring

Filter by subscription status.

List Subscriptions Response

Create Subscription

Use Case

Creates an address subscription to monitor blockchain activity. Matching events are POSTed to webhook_url.

Create Subscription

Request Body
1
addressstringRequired

On-chain address to monitor.

2
chainstringRequired

Blockchain the address lives on (e.g., `ethereum`, `tron`).

3
webhook_urlstring (url)Required

HTTPS endpoint that will receive delivery events.

4
networkstring

Network within the chain (e.g., `mainnet`, `testnet`).

5
event_typestring

Specific event type to monitor (e.g., `transfer`). Defaults to all event types.

6
labelstring

Free-form label for your own bookkeeping.

7
metadataobject

Arbitrary key-value JSON returned back on every subscription read.

Example Payload

Create Subscription Response
Same shape as List Subscriptions 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.

Create Subscription Response

Get Subscription

Use Case

Returns a single subscription by ID.

Get Subscription

Get Subscription Response
Same shape as List Subscriptions 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 Response

Update Subscription

Use Case

Partially updates a subscription. Only event_type and webhook_url can be changed.

Update Subscription

Request Body
1
event_typestring

Updated event type to monitor.

2
webhook_urlstring (url)

Updated webhook endpoint.

Example Payload

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.

Delete Subscription

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.

One-time secret

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

Rotate Signing Secret Response
1
objectstring

Resource type identifier. Always `signing_secret`.

2
signing_secretstring

The new HMAC signing secret. Returned only on this response — store it before the response closes.

Rotate Signing Secret Response

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.

List Delivery Events

Query Parameters
1
starting_afterstring

Opaque cursor — pass `next_cursor` from a prior response to fetch the next page.

2
ending_beforestring

Opaque cursor for reverse pagination.

3
limitinteger

Page size.

4
statusstring

Filter by delivery status: `pending`, `delivered`, or `failed`.

5
subscription_iduuid

Narrow to a single subscription.

List Delivery Events Response

Get Delivery Event

Use Case

Returns a single delivery event by ID. The event must belong to the caller's organization.

Get Delivery Event

Get Delivery Event Response
Same shape as List Delivery Events 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.

Get Delivery Event Response

Retry Delivery Event

Use Case

Re-queues a specific delivery for another attempt. Useful for delivering events that previously failed.

Retry Delivery Event
Did you find this page useful?

Join our Discord