Developer API
Programmatic access to stablecoin freeze data. Requires an API key - create one from your account.
Send your key as a bearer token on every request:
curl https://blocklist.fyi/api/v1/events \ -H "Authorization: Bearer bl_live_…"
Every response includes X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset (Unix seconds) headers. Exceeding a limit returns 429 with a Retry-After header.
Errors use a consistent envelope - { "error": { "code", "message", "field"? } } - so you can branch on the stable code.
Building an integration or agent? Grab the machine-readable OpenAPI spec or the llms.txt guide.
- Free: 10/min · 100/day · up to 10 rows/request
Paginated freeze ledger. Filters: chain, asset (USDT|USDC), status (BLACKLISTED|UNBLACKLISTED|PENDING|DESTROYED), address (partial match), from/to (ISO dates), cursor, limit(capped at your tier’s rows/request, above). Each event includes a has_intel boolean.
Single event with its multi-sig timeline. Includes has_intel flag.
Full freeze history for one address across all chains. Returns an events array, each with has_intel. An empty array means the address has never been frozen.
The valid intel category names. Fetch before submitting - unknown categories are silently dropped.
Submit community intelligence on a frozen address. Identify the target by address (resolved to its latest freeze, matched across encodings; optional chain) or an exact event_id. Plus entity_name (4–100 chars), description (10–500 chars), evidence_urls (array, ≥1 https URL, max 3), categories (optional array). Notes are held as PENDING until verified by a moderator; an identical resubmission returns the existing note with duplicate: true.
Your own intel submissions, newest first, with moderation outcomes: status (PENDING|VERIFIED|REJECTED), rejection_reason, admin_feedback (moderator coaching), and confidence. Filters: status, since (ISO timestamp - only notes updated at/after it, for delta sync), cursor, limit. Poll this to learn why submissions were accepted or rejected.