/cerlive/exchanges

POST /api/cerlive/exchanges

Price: 1 credit

Get a crypto exchange security profile by exchange id

How to use it

Get the full CER.live security profile of a cryptocurrency exchange by its id. Returns the overall security rating, server and user security scores, penetration-test / proof-of-reserves / bug-bounty scores, ISO 27001 / CCSS / funds-insurance flags, total / BTC / ETH balances, trading volume, rank, country, certificates (proof of funds, bug bounty, penetration test) with their links and validity, bug-bounty programs with rewards and scoring, social links, and the ids of cryptocurrencies listed on the exchange.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• eid string required — Exchange id (the slug used in the cer.live exchange URL) (examples: "binance", "coinbase-exchange", "kraken"; minLength: 1)

Response

• @type string (default: "CerliveExchange")
• id integer required
• alias string required
• name string required
• display_name string nullable
• status string nullable
• country string nullable
• link string nullable
• image string nullable
• description string nullable
• coingecko_id string nullable
• is_cg_listed boolean (default: false)
• year_established integer nullable
• rank integer nullable
• category_id integer nullable
• rating number nullable
• server_security integer nullable
• user_security integer nullable
• penetration_tests integer nullable
• proof_of_reserves integer nullable
• bug_bounty integer nullable
• iso boolean (default: false)
• ccss boolean (default: false)
• funds_insurance boolean (default: false)
• has_past_incidents boolean (default: false)
• total_balance number nullable
• btc_balance number nullable
• eth_balance number nullable
• trading_volume number nullable
• certificates array (default: [])
  • @type string (default: "CerliveCertificate")
  • name string required
  • link string nullable
  • active_until 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
• social_references array (default: [])
  • @type string (default: "CerliveSocialReference")
  • url string required
  • social_network_id integer nullable
• project_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 — Exchange 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.