/resolve/tokens

POST /api/resolve/tokens

Price: 20 credits

Every record our sources hold about one crypto token, from its contract and network, a token page URL or one of its identifiers, with follow-up calls for its market and on-chain data.

How to use it

Use when you hold something that identifies one fungible crypto token: contract with network for an on-chain address, url for its CoinGecko, CoinMarketCap or block explorer page, or id with id_type for a bare identifier such as a CoinGecko id (id_type coingecko_coin). Returns each source's record whole, the token's identifiers (contracts per network among them) and ready follow-up calls in next, whose params pass as-is.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• url string nullable — A token's page on CoinGecko, CoinMarketCap or a block explorer (Etherscan, BscScan, PolygonScan, Arbiscan, BaseScan, Solscan) (examples: "https://www.coingecko.com/en/coins/wormhole", "https://etherscan.io/token/0xb0ffa8000886e57f86dd5264b9582b2ad87b2b91")
• contract string nullable — Token contract address: 0x-hex on EVM networks, base58 on Solana; requires network (examples: "0xb0ffa8000886e57f86dd5264b9582b2ad87b2b91")
• network string nullable — Network the contract lives on, in lower case; requires contract (examples: "ethereum", "bsc", "solana", "base", "arbitrum", "polygon")
• id string nullable — Token identifier of the kind named by id_type; requires id_type (examples: "wormhole")
• id_type string nullable — Kind of identifier given in id; requires id (one of: "coingecko_coin", "coinglass_symbol", "coinmarketcap_coin", "coinmarketcap_coin_id", "dappradar_token", "messari_asset", "zerion_fungible"; examples: "coingecko_coin")

Response

• @type string (default: "ResolvedToken")
• id string nullable — Strongest identifier of the token, as type:value (examples: "coingecko_coin:wormhole")
• links array — Records tied to the token, strongest first (default: [])
  • @type string (default: "ResolvedTokenLink")
  • source string required — Platform the record comes from (examples: "coingecko")
  • endpoint string required — Endpoint that returned the record, callable as it is (examples: "coingecko/coins")
  • record object required — The record exactly as that endpoint returns it
  • confidence number required — Confidence that the record is this token, 0 to 1
  • method string required — How the record was tied to the token: input_id (fetched by the given identifier), <identifier>_match (carries an identifier the token holds), hub_link (reached through a linked record's identifier) (examples: "contract_match")
  • evidence string required — The field and value that tie the record to the token
  • partial boolean — The source stopped before it answered in full (default: false)
• identifiers object — Every identifier of the token found in the records, by type: the primary value, the platforms carrying it and the other values found (default: {})
  • * object
    • @type string (default: "ResolvedIdentifier")
    • value string required — Identifier value (examples: "stripe.com")
    • sources array required — Platforms whose records carry this value
    • alternatives array — Other values of the same identifier carried by the records, most carried first (default: [])
      • @type string (default: "IdentifierValue")
      • value string required — Identifier value (examples: "stripe.com")
      • sources array required — Platforms whose records carry this value
• not_found object — Endpoints checked that gave no record, grouped by why
  • @type string (default: "NotFound")
  • no_record array — Endpoints that answered without a record (default: [])
  • error array — Endpoints that failed to answer (default: [])
  • timeout array — Endpoints that ran out of their time budget (default: [])
  • skipped array — Endpoints that do not take the identifier they were given (default: [])
• next array — Follow-up calls for this token's market and on-chain data, each with its payload filled in (default: [])
  • @type string (default: "NextCall")
  • endpoint string required — Endpoint to call next (examples: "webparser/render")
  • params object required — Its payload, ready to send (examples: {"url":"https://stripe.com"})

Errors

• 422 — Not exactly one of url, contract with network, or id with id_type; or the value is not of that kind. Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No source holds a record of this token. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.