Actions77
- Address History Actions
- Address Latest Actions
- AML Actions
- Block Data Actions
- Blockchain Event Actions
- Blockchain Fee Actions
- Estimate Contract Interaction Gas
- Estimate FA1.2 Transfer Fee
- Estimate FA2 Transfer Fee
- Estimate Native Coin Transfer Compute Units
- Estimate Native Coin Transfer Gas
- Estimate Program Invocation Compute Units
- Estimate Token Transfer Compute Units
- Estimate Token Transfer Gas
- Estimate Transaction Smart Fee
- Estimate Transfer Fee
- Get EIP-1559 Fee Recommendations
- Get Fee Recommendations
- Broadcast Actions
- Contract Actions
- HD Wallet Actions
- Market Data Actions
- Prepare Transaction Actions
- Simulate Actions
- Transaction Data Actions
- Utility Actions
Blockchain Event → Create Subscription
AI-generatedSummary
Create a Crypto APIs webhook subscription for a selected blockchain event type. The node sends the event-specific subscription details to the API and returns the created subscription.
Inputs
- Event Type (required) — Choose one of eight supported events: unconfirmed or confirmed coin transactions, confirmed token or internal transactions, their each-confirmation variants, or block mined.
- Callback URL (required) — Webhook URL that will receive event notifications.
- Callback Secret Key — Optional secret key for verifying callback signatures.
- Allow Duplicates — Whether to allow duplicate subscriptions for the same address and event; defaults to false.
- Blockchain (required) — Select a blockchain supported by the chosen event type.
- Network (required) — Select a network supported by the chosen event type and blockchain.
- Address (required) — Address to monitor for address-based events. Not shown for Block Mined.
- Confirmations Count (required) — For each-confirmation event types, the number of confirmations to track.
- Receive Callback On — For confirmed event types without each-confirmation behavior, optionally specify the exact confirmation number for the callback; 0 selects the default behavior.
Output shape
A single subscription record.
The source uses the selected event type to choose a dedicated API endpoint and sends the applicable fields in the API request. The available blockchain and network choices vary by event type.