/cerlive/wallets

POST /api/cerlive/wallets

Price: 1 credit

Get a crypto wallet security profile by wallet id

How to use it

Get the full CER.live security profile of a cryptocurrency wallet by its id. Returns the overall security rating and rank, the wallet platform (android / ios / chrome / brave / …) and platform type, the pentest / bug-bounty / past-incidents / security-features score components, the supported blockchains, app-store rating with installation and review counts, the company incorporation, data-safety and cookie policy links, the security features the wallet supports, third-party audits with auditor and score, bug-bounty programs with rewards and scoring, key-restore methods with their custody model and authentication factors, and known past incidents.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• uid string required — Wallet id (the wallet/platform identifier used by cer.live, e.g. okx-android) (examples: "okx-android", "zengo-android", "coolwallet-ios"; minLength: 1)

Response

• @type string (default: "CerliveWallet")
• id integer required
• uid string required
• name string required
• rating number nullable
• rank integer nullable
• image string nullable
• description string nullable
• link string nullable
• incorporation string nullable
• wallet_id integer nullable
• wallet_platform_name string nullable
• wallet_platform_type_name string nullable
• application_rating number nullable
• installation_count integer nullable
• review_count integer nullable
• data_safety_policy_url string nullable
• cookie_policy_url string nullable
• pentest_rating number nullable
• bug_bounty_rating number nullable
• past_incidents_rating number nullable
• security_features_rating number nullable
• blockchains array (default: [])
• features array (default: [])
  • @type string (default: "CerliveWalletFeature")
  • feature_id integer required
  • value string nullable
• audits array (default: [])
  • @type string (default: "CerliveWalletAudit")
  • auditor_name string nullable
  • auditor_icon string nullable
  • type string nullable
  • scope string nullable
  • link string nullable
  • date integer nullable
  • score number nullable
  • scope_score number nullable
  • relevance_score number 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
• restore_methods array (default: [])
  • @type string (default: "CerliveWalletRestoreMethod")
  • name string required
  • score number nullable
  • score_weight number nullable
  • link string nullable
  • asset_name string nullable
  • custody string nullable
  • authentication_factors array (default: [])
• incidents array (default: [])
  • @type string (default: "CerliveWalletIncident")
  • description string required
  • team_reaction string nullable
  • severity_items 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 — Wallet 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.