Documentation Index
Fetch the complete documentation index at: https://docs.coingecko.com/llms.txt
Use this file to discover all available pages before exploring further.
cg.coin.info.updated
This event is triggered whenever there is an update to the core information of a coin.
Potential Use Cases
Automated Asset Updates for Wallets & Exchanges
Instantly update your platform’s UI when a token undergoes a rebrand, changes its ticker symbol, is assigned a new
category, or updates its official logo (image updates).Cross-Chain Contract Monitoring
Automatically detect when an existing project deploys on a new blockchain, or when a token migrates to a new smart contract address (
platforms additions/removals).Risk Management & Compliance
Act immediately when CoinGecko adds critical alerts to a coin, such as a warning about a malicious activity or contract address migration notice (
public_notices).Bots & Alert Systems
Build automated bots that notify your community, the moment a project updates its whitepaper, GitHub repository, or official social media links.
References based on CoinGecko coin page

Data References
The webhook will only listen for and dispatch payloads for changes in the following data fields:| Data Field | Description & Output Field Example |
|---|---|
id | API ID of a coin. e.g.
The API ID serves as the primary unique identifier. It is typically immutable, except when an update is required to resolve unforeseen errors. You can also retrieve the full coin id list via this /coins/list endpoint or visit respective coin page on CoinGecko.com |
symbol | Ticker symbol of a coin. e.g.
|
name | Name of a coin. e.g.
|
web_slug | URL Slug of a coin on CoinGecko.com. e.g.
web_slug can be different from coin_id, use web_slug when you want to obtain the URL of a coin page on CoinGecko.com. |
platforms.{asset_platform_id}
| Token contract address of a coin. e.g.
You can get the full list of asset platforms id via this endpoint. In edge cases involving changes to the asset_platform_id itself (e.g., migrating from xdai to ethereum), the system will send two changes:
|
categories | Categories of a coin, e.g.
|
public_notices | Public notices of a coin, including: security breach information and contract migration announcements. e.g.
|
additional_notices | Additional notices of a coin: can mint new tokens, has unverified contract |
links.{site}
| Official websites and social media sites of a coin. e.g.
update’ event will be triggered and the payload will contain an array of multiple links. If a link is being removed, it will return empty value:
|
image | Image file name of a coin. e.g.
Instead of tracking the image.thumb URL in the payload, the webhook returns the image_file_name (e.g., uniswap-logo.png). |
Payload
Each webhook payload contains a specific event ID, timestamp, and adata object detailing the exact fields that changed.
Payload Structure
event_type:cg.coin.info.updateddata:id: CoinGecko coin ID (e.g.,bitcoin)symbol: Coin symbol (e.g.,btc)name: Coin name (e.g.,Bitcoin)changes: An array of objects detailing the modifications. A single payload can contain one or multiple field changes.field: The specific field that was altered.change_type: Represents the action (addition,update, orremoval).new_value: The updated value (returnsnullifchange_typeisremoval).old_value: The previous value (returnsnullifchange_typeisaddition).


