Keep your application synchronized with CoinGecko in real-time — no cron jobs or polling required. Listen to events like cg.coin.info.updated and react instantly to changes.
Automated Asset Updates
Update your UI when a token rebrands, changes ticker, or updates its logo.
Cross-Chain Monitoring
Detect when a project deploys on a new chain or migrates a contract address.
Risk & Compliance
Act immediately on critical alerts — malicious activity warnings or contract migration notices.
CoinGecko Webhooks (Beta) is available for paid plan customers (Analyst plan & above).
Credit charge: 10 credits per event delivery. Retry attempts are not charged.
Maximum webhook endpoints: 5.
Enterprise clients who need higher limits — contact your Customer Success Manager.
CoinGecko Webhooks is a supplementary delivery mechanism for real-time notifications. Currently in beta — excluded from the SLA applicable to the CoinGecko API Platform.
Share Feedback
Help us improve Webhooks — share your suggestions and use cases.
Verify that incoming payloads are genuinely from CoinGecko by computing an HMAC SHA256 hash and comparing it to the x-cg-signature header.Signing string format:{timestamp}:{event_id}:{json_body}
The {json_body} must be the raw, unparsed request body — not a re-stringified JSON object.
If your framework auto-parses JSON before verification, the signature will fail.
Send Test Event — dispatches a mock cg.coin.info.updated payload. Use it to verify your server receives the request and responds with 2xx before going live.
Delivery Logs — view the latest 100 delivery attempts. Use these to identify if your endpoint is rejecting requests.
Each delivered webhook event consumes 10 credits. The cg.coin.info.updated event listens to all active coins on CoinGecko — volume fluctuates based on market activity and how frequently projects update their metadata.
Expected volume: up to 200 updates/day based on historical data.
If your server fails to respond with a 2xx status code, CoinGecko will retry with exponential backoff. Retry attempts are not charged.A webhook is automatically disabled under either condition:
Condition
Threshold
Single event backoff
14 failed retries over ~24 hours
Aggregate failure cap
300 failed retries across 12 hours
When a webhook is disabled, you’ll receive an email notification. To resume: