/cerlive/tokens

POST /api/cerlive/tokens

Price: 1 credit

Get a crypto coin/token security profile by token id

How to use it

Get the full CER.live security profile of a cryptocurrency coin or token by its id. Returns the overall security rating, audit coverage, market cap, price, trading volume and supply, token and platform audits with auditor names and report links, bug-bounty programs, insurance coverage, incident and ongoing bug-bounty flags, social links, and the ids of exchanges the token is listed on.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• eid string required — Token id (the slug used in the cer.live token URL) (examples: "1inch", "aave", "uniswap"; minLength: 1)

Response

• @type string (default: "CerliveToken")
• id integer required
• alias string required
• name string required
• ticker string nullable
• link string nullable
• image string nullable
• category string nullable
• rank integer nullable
• details_level string nullable
• rating number nullable
• audit_coverage integer nullable
• market_cap number nullable
• market_cap_change number nullable
• price number nullable
• price_change number nullable
• trading_volume number nullable
• total_supply number nullable
• circulation_supply number nullable
• is_token_audit_relevant boolean (default: false)
• is_platform_audited boolean (default: false)
• has_ongoing_bug_bounty boolean (default: false)
• has_insurance boolean (default: false)
• has_incidents boolean (default: false)
• token_audits array (default: [])
  • @type string (default: "CerliveAudit")
  • auditor_name string nullable
  • auditor_icon string nullable
  • audit_url string nullable
  • total_score number nullable
  • platform_uid string nullable
  • audited_at integer nullable
• platform_audits array (default: [])
  • @type string (default: "CerliveAudit")
  • auditor_name string nullable
  • auditor_icon string nullable
  • audit_url string nullable
  • total_score number nullable
  • platform_uid string nullable
  • audited_at integer nullable
• bug_bounties array (default: [])
  • @type string (default: "CerliveBugBounty")
  • auditor_name string nullable
  • auditor_icon string nullable
  • status string nullable
  • reward string nullable
  • language string nullable
  • scope_url string nullable
  • score number nullable
  • scope_description_score number nullable
  • acceptance_score number nullable
  • third_party_score number nullable
  • language_score number nullable
• insurances array (default: [])
  • @type string (default: "CerliveInsurance")
  • auditor_name string nullable
  • link string nullable
• social_references array (default: [])
  • @type string (default: "CerliveSocialReference")
  • url string required
  • social_network_id integer nullable
• exchange_ids array (default: [])
• created_at integer nullable
• updated_at integer nullable

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.