/cerlive/tokens/search

POST /api/cerlive/tokens/search

Price: 5 credits

Search the CER.live catalog of rated crypto coins and tokens

How to use it

List CER.live rated cryptocurrency coins and tokens. Each result carries the project's overall security rating, category, market cap, audit coverage, rank, market data (price, trading volume, supply), counts of token / platform audits, bug-bounty programs, insurances and social links, and flags for ongoing bug bounty, insurance, platform audit and past incidents.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of results (min: 1)

Response

• @type string (default: "CerliveTokenListItem")
• id integer required
• alias string nullable
• name string required
• category string nullable
• image string nullable
• rating number nullable
• rank integer nullable
• market_cap number nullable
• audit_coverage integer nullable
• details_level string nullable
• price number nullable
• price_change number nullable
• market_cap_change number nullable
• trading_volume number nullable
• total_supply number nullable
• circulation_supply number nullable
• token_audit_count integer (default: 0)
• platform_audit_count integer (default: 0)
• bug_bounty_count integer (default: 0)
• insurance_count integer (default: 0)
• social_reference_count integer (default: 0)
• 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)
• 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 — The entity was not found, or a precondition failed 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.