/zerion/fungibles

POST /api/zerion/fungibles

Price: 1 credit

Get a token's price and market profile by its Zerion token id

How to use it

Get the full market profile of a crypto token by its Zerion token id (resolve a symbol via the search endpoint). Returns name, symbol, icon, verification, current price, market cap, fully diluted valuation, circulating and total supply, price-change percentages over multiple windows, a description, and the per-chain contract addresses.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• fungible_id string required — Zerion token id, as returned by the search endpoint (examples: "BTC-ee9702a0-c587-4c69-ac0c-ce820a50c95b", "eth"; minLength: 1)
• currency string — Currency to denominate price and market data in (default: "usd"; one of: "usd", "eur", "gbp", "jpy", "aud", "cad", "chf", "cny", "inr", "krw", "rub", "brl", "try", "btc", "eth")

Response

• @type string (default: "ZerionFungible")
• id string required
• name string nullable
• symbol string nullable
• image string nullable
• is_verified boolean nullable
• description string nullable
• price number nullable
• market_cap number nullable
• fully_diluted_valuation number nullable
• circulating_supply number nullable
• total_supply number nullable
• change_1d number nullable
• change_30d number nullable
• change_90d number nullable
• change_365d number nullable
• contracts object (default: {})
  • * string

Errors

• 422 — The request body did not validate 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 — Token not found 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.