Blockchain API

Watch an Ethereum, Polygon, BNB, Arbitrum, Base or Optimism Address with Webhooks

POST /eth/webhooks

The same endpoint works on every EVM chain: POST /polygon/webhooks, /bnb/webhooks, /arbitrum/webhooks, /base/webhooks and /optimism/webhooks. Everything on this page applies to each of them, with that chain's native coin (POL on Polygon, BNB on BNB Smart Chain, ETH on the others) in place of ETH.

#Request

curl -X POST https://blockchainapi.qoest.com/eth/webhooks \
  -H "Authorization: Bearer your-token" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Treasury",
    "address": "0x2222222222222222222222222222222222222222",
    "webhook_url": "https://example.com/hooks/eth"
  }'

#Parameters

Name Type Required Notes
name string yes Your label, up to 255 characters.
address string yes A mainnet address on that chain: 0x followed by 40 hex characters.
webhook_url string yes The URL that receives the deliveries.

Sending the same address and webhook_url again updates that webhook. The response matches the Bitcoin webhook, with blockchain_type set to the chain:

Chain blockchain_type
Ethereum 1
Polygon 2
BNB Smart Chain 3
Arbitrum One 4
Base 5
OP Mainnet 6

List, get and delete work the same way at /{chain}/webhooks and /{chain}/webhooks/{id}. A webhook is only reachable under its own chain's path.

#What Gets Sent

  • Native coin transactions (ETH, POL or BNB) with a non-zero value, sent with "type": "transaction".
  • ERC-20 transfers with a non-zero amount, sent with "type": "transfer" and the token's name, symbol and decimals. Only tokens whose contract is verified on that chain's Etherscan explorer are sent.
  • Transfers from an address to itself are skipped.
  • One delivery per transaction hash: if a transaction moves several tokens, only the first is sent.

See Webhook Payloads for both bodies.