/goplus/token-approvals

POST /api/goplus/token-approvals

Price: 10 credits

List a wallet's ERC-20 token approvals with per-spender risk by chain and wallet address

How to use it

Audit a wallet's outstanding ERC-20 token approvals (allowances) on a chain. Returns each approved token (address, name, symbol, decimals, balance, open-source and malicious flags) together with the list of spenders it has been approved to, including the approved amount, first and latest approval times and transaction hashes, and a risk profile of each spender contract (name, tag, creator, contract / trust-list / doubt-list status, deployment time and malicious behaviors). Use to power a revoke-approvals flow. Returns an empty list when the wallet has no approvals.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• chain_id string required — Blockchain network to scan the wallet on (one of: "1", "10", "25", "56", "100", "130", "137", "146", "169", "177", "196", "204", "321", "324", "480", "1868", "1625", "1514", "1030", "2818", "2741", "4200", "5000", "8453", "59144", "43114", "42766", "42161", "81457", "80094", "200901", "201022", "534352", "48900", "688688", "810180", "tron")
• address string required — Wallet address to audit approvals for (examples: "0x28c6c06298d514db089934071355e5743bf21d60"; minLength: 1)

Response

• @type string (default: "GoplusApprovedToken")
• address string required
• chain_id string nullable
• name string nullable
• symbol string nullable
• decimals integer nullable
• balance number nullable
• is_open_source boolean nullable
• is_malicious boolean nullable
• malicious_behavior array (default: [])
• approvals array (default: [])
  • @type string (default: "GoplusTokenApproval")
  • approved_contract string required
  • approved_amount string nullable
  • approved_at integer nullable
  • initial_approval_at integer nullable
  • initial_approval_hash string nullable
  • tx_hash string nullable
  • spender object nullable
    • @type string (default: "GoplusSpenderInfo")
    • name string nullable
    • tag string nullable
    • creator_address string nullable
    • is_contract boolean nullable
    • doubt_list boolean nullable
    • trust_list boolean nullable
    • is_open_source boolean nullable
    • deployed_at integer nullable
    • malicious_behavior array (default: [])

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.