/cerlive/wallets/search

POST /api/cerlive/wallets/search

Price: 5 credits

List crypto wallets ranked by their CER.live security rating

How to use it

List cryptocurrency wallets rated by CER.live, ordered by security rating. Each item returns the wallet name, security rating, supported platform (e.g. android, ios, chrome, brave) and platform type, the company incorporation, and how many security features it has. Use a wallet id with the 'wallets' endpoint for the full wallet profile.

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 wallets to return (min: 1)

Response

• @type string (default: "CerliveWalletListing")
• id integer required
• uid string required
• name string required
• wallet_id integer nullable
• rating number nullable
• rank integer nullable
• image string nullable
• link string nullable
• description string nullable
• incorporation string nullable
• wallet_platform_name string nullable
• wallet_platform_type_name string nullable
• feature_count integer nullable
• application_rating number nullable
• review_count integer nullable
• installation_count integer nullable
• data_safety_policy_url string nullable
• cookie_policy_url string nullable
• 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.