Create a subscription

/v4/subscription

50 credits per sent Notification + 50 credits per day per subscription

Create and manage blockchain event notification subscriptions. This endpoint allows you to receive real-time webhook alerts for address activity, token transfers, and native currency transactions across supported blockchains.

Tip: Notifications are formatted using Templates. We recommend using the enriched template because it provides clean, human-readable enhanced data with token metadata. Learn more: 👉 Learn more

Supported Notification Types:

  • ADDRESS_EVENT – Triggered for any address-level transaction or event.
  • INCOMING_FUNGIBLE_TX / OUTGOING_FUNGIBLE_TX – Detects ERC20 or equivalent token transfers.
  • INCOMING_NATIVE_TX / OUTGOING_NATIVE_TX – Detects native currency transfers (ETH, MATIC, etc.).

For more subscription types & chain support, see: 👉 Subscriptions Overview

Restrictions

Each subscription must be unique within your API key based on the following fields. If a matching subscription already exists, creation will be rejected:

  • Address subscriptions (ADDRESS_EVENT, INCOMING/OUTGOING_NATIVE_TX, etc.) – unique by type + chain + address + url
  • Contract log subscriptions (CONTRACT_ADDRESS_LOG_EVENT) – unique by type + chain + contractAddress + event + url
  • Block subscriptions (FAILED_TXS_PER_BLOCK) – unique by type + chain + url

To monitor the same address with different configurations (e.g. different conditions or finality), use a different webhook URL for each subscription.

Webhook Response Format

Recommended Default: templateId = "enriched"

If you do not specify a custom template, the response will use the legacy format. However, the enriched template is recommended because it provides structured, human-readable fields and token metadata.

To learn about legacy format, custom templates, or enriched_with_raw_data, visit: 👉 Learn more

Example: Enriched Template Webhook Payload

  {
    "data": {
      "kind": "transfer",
      "blockHash": "0x1234567890abcdef...",
      "blockNumber": 18500000,
      "blockTimestamp": 1699123456,
      "txId": "0xabcdef1234567890...",
      "currency": "ETH",
      "txTimestamp": 1699123456,
      "from": "0x742d35Cc6634C0532925a3b8D4C9db96C4b4d8b6",
      "to": "0x8ba1f109551bD432803012645Hac136c",
      "value": "1000000000000000000",
  "contractAddress": "0xA0b86a33E6441b8c4C8C0C8C0C8C0C8C0C8C0C8C0C",
  "tokenId": "12345",

  "additionalData": {
    "gasUsed": "21000",
    "gasPrice": "20000000000"
  },

  "tokenMetadata": {
    "type": "nft",
    "decimals": 0,
    "symbol": "NFT",
    "name": "My NFT",
    "uri": "https://api.example.com/metadata/12345"
  },

  "subscriptionId": "64f1a2b3c4d5e6f7g8h9i0j1",
  "subscriptionType": "ADDRESS_EVENT"
},
"location": "...",
"scheme": "..."

}

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
enum
required

Type of the subscription.

Allowed:
attr
object
required

Additional attributes based on the subscription type.

boolean

Flag indicating whether the subscription should include mempool transactions. Only available on BTC blockchain.

string
enum

Choose between speed (confirmed) and block confirmations on chain (final). Only available on TRON and EVM for now (v4).

Allowed:
string
enum

Configure the response format. Only available on TRON and EVM for now (v4).

Allowed:
Responses

Language
Credentials
Header
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json