Token approval risk

Check 1–50 spender addresses before a user signs an approve or permit: each spender gets its own risk assessment and state.

POSThttps://triport.io/v1/intelligence/approval-risk

Network: Ethereum
Scope: intelligence:read
Auth: x-token: $TRIPORT_API_KEY header (or Authorization: Bearer)
Rate limit: Business — 30 rps (intelligence, burst ×2); Enterprise — 150 rps

Request

cURLJavaScriptPython

curl -X POST "https://triport.io/v1/intelligence/approval-risk" \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"spenders":[{"chain":"eth","address":"0x6b175474e89094c44da98b954eedeac495271d0f"}]}'

const res = await fetch("https://triport.io/v1/intelligence/approval-risk", {
  method: "POST",
  headers: {
    "x-token": process.env.TRIPORT_API_KEY,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "spenders": [
      {
        "chain": "eth",
        "address": "0x6b175474e89094c44da98b954eedeac495271d0f"
      }
    ]
  }),
});
const data = await res.json();
console.log(data);

import os


import requests


resp = requests.post(
    "https://triport.io/v1/intelligence/approval-risk",
    headers={
        "x-token": os.environ["TRIPORT_API_KEY"],
        "Content-Type": "application/json",
    },
    json={
        "spenders": [
            {
                "chain": "eth",
                "address": "0x6b175474e89094c44da98b954eedeac495271d0f",
            },
        ],
    },
)
data = resp.json()
print(data)

Response

JSON

Example

{
  "state": "partial",
  "meta": {
    "cached": false,
    "complete": false
  },
  "data": {
    "items": [
      {
        "index": 0,
        "spender": {
          "chain": "eth",
          "address": "0x6b175474e89094c44da98b954eedeac495271d0f"
        },
        "assessment": {
          "address": "0x6b175474e89094c44da98b954eedeac495271d0f",
          "chain": "eth",
          "risk": {
            "value": null,
            "level": "unknown"
          }
        },
        "state": "partial"
      }
    ]
  }
}

Check 1–50 spender addresses before a user signs an approve or permit: each spender gets its own risk assessment and state.

This checks the spenders you supply. It does not discover a wallet's existing allowances and it never changes one. Each spender counts as one request against the per-second limit.

Released on Ethereum. Any other chain value answers 422 with state unsupported. More chains are coming; see the changelog.

Every answer is an envelope with state, meta, optional data and optional error. Read state first: ok, empty, partial, stale, unsupported or unavailable (see response states). meta.cached tells you whether the answer came from cache.

Parameters

freshbooleanoptional

Optional. true skips the cache and asks for a new lookup (GET routes: ?fresh=1).

spendersarray of objectrequired

1–50 {chain, address} objects: the spender contracts a user is asked to approve. Each one counts as one request against the per-second limit.

Response

Illustrative response; values are examples, not a recorded observation.

Errors

HTTP	`error.code`	When
400	`invalid_request`	Malformed address, unknown field, `null` value or invalid JSON.
401	`unauthorized`	Missing or invalid API key.
403	`scope_missing` / `tier_insufficient`	The key lacks `intelligence:read`, or the plan is below Business.
405	`method_not_allowed`	Wrong HTTP method; the `Allow` header names `POST`.
422	`unsupported`	The chain (or the contract) is not supported by this method.
429	`rate_limited`	Over the `intelligence` per-second limit; wait `Retry-After` seconds.
503	`unavailable`	The lookup could not be completed right now; retry later.
504	`timeout`	The lookup took too long; retry, or retry later with the same input.

See errors, limits and states for the full rules and the code examples.