Skip to main content

​
v1.7.15: 30 July 2026

​
New fields

Platform API:
  • Connection transactions (CanonicalConnectionTransactionDto): provider_transaction_id on persisted reads; id is the stable DB row id on persisted reads (provider-native id on live adapter responses). transaction_id matches id when present.

​
Behavior changes

Data API:
  • Duplicate OpenAPI operation summaries uniquified so Mintlify pages no longer collide on slugs (Get Address Details, Get Address Info with Risk Score, Get Asset Flow for an Address, Get Top USD/Asset Balances by Address, Get Connections by Address).

​
v1.7.14: 29 July 2026

​
New account-connection providers

Platform API:
  • fordefi: custodial wallets via API User bearer token
  • coins_ph: Coins.ph exchange accounts via API key and secret
  • fireblocks: Fireblocks custody via API user id and RSA private key (optional region)
  • pave_bank: Pave Bank accounts via OAuth client credentials (optional environment)
  • quickbooks: QuickBooks Online ledger connection (kind: ledger) via OAuth authorize URL + realm/state

​
New endpoints

Platform API:
  • POST /v2/account-connections/quickbooks/authorize-url: start QuickBooks OAuth; returns authorize_url and CSRF state
  • GET /v2/account-connections/transactions/sync/status: poll a sync batch (batch_id); authoritative completion is complete
  • GET /v2/account-connections/bookkeeping/{connectionId}/counterparties: preview customers/vendors from a ledger connection
  • GET /v2/account-connections/bookkeeping/{connectionId}/categories: preview P&L category candidates from a ledger connection
Data API:
  • GET /v2/transaction-categories: list default + workspace-custom transaction categories
  • POST /v2/transaction-categories: create a custom category (idempotent on name)
  • PUT /v2/transaction-categories/{id}: rename a custom category

​
New fields

  • Account connections gain kind (account | ledger), last_synced_at, and sync_status; GET /v2/account-connections accepts kind (defaults to account)
  • GET /v2/addresses/workspace/balances: each balance includes account_id (joins to AccountDto.id); response schema is WorkspaceBalancesResponseDto
  • AssetBalanceDto / account balance payloads: amount and usd are decimal strings (usd is null when unknown); assets gain name
  • Counterparties list: optional include_addresses=true returns each counterparty’s saved addresses inline
  • Risk v2 config behaviours: optional tokens[] on watched-token (max 200)
  • GET /v2/risk/signals: each attribution signal includes a description; catalogue adds eight signals (ransomware, eu-sanctioned, eu-sanction-ru, uk-sanctioned, japan-sanctioned, france-sanctioned, fbi-fraud, nbctf-terror-financing) and behaviours token-activity / watched-token

​
Behavior changes

  • Altitude-connected accounts classify as bank (previously multisig)
  • Transfer enrichment category upserts accept any workspace-resolved category name (defaults ∪ custom), not a fixed enum; defaults gain Swap and Airdrop
  • Range MCP: 85 tools — adds documentation tools (get_range_overview, search_documentation, get_documentation) and four mutating tools (add_accounts, create_counterparty, add_counterparty_addresses, create_alert_rule) gated to workspace members with EDITOR role or higher

​
v1.7.13: 22 July 2026

​
New endpoints

Platform API:
  • GET /v2/account-connections/transactions/{transactionId}: fetch one persisted connection transaction by id
  • GET /v2/multisig/details: stateless multisig read (config, members, balances, pending proposals) without saving a connection

​
New fields

  • POST /v2/accounts/refresh: response gains failures[] (account_id, label, reason) — always present; length matches failed

​
Behavior changes

  • POST /v2/account-connections (Safe / Squads / Realms): failed multisig resolve returns a classified error body with code one of invalid_address, multisig_not_found, wrong_network (Safe only), or upstream_unavailable
  • GET /v2/risk/address / batch: rejects inputs that cannot be a real address (empty, too short/long, whitespace, or characters outside address alphabets) with 400 instead of scoring them as severity: none
  • GET /v2/risk/signals: velocity behaviour description updated to pass-through / money-mule framing (EVM Risk v2 now uses ClickHouse Rule B + Rule A; Solana keeps Redis velocity)

​
v1.7.11 (hotfix): 17 July 2026

​
New account-connection providers

Data API:
  • altitude: connect Squads-based Solana smart accounts via a deposit or Settings address
  • revolut_business: connect Revolut Business accounts via OAuth refresh token and API certificate
  • turnkey: connect Turnkey-managed wallets via API key pair and organization id

​
New endpoints

  • PATCH /v2/account-connections/transactions/{transactionId}/category: set a user-assigned category label on a persisted connection transaction. The category survives subsequent provider re-syncs.
  • GET /v2/accounts/concentration: asset, venue, and network concentration computed over the stored balances of the caller workspace accounts (refresh=true to refresh balances first).

​
New fields

  • GET /v2/account-connections/transactions: response gains meta.next_cursor; new cursor, start_time, end_time, status, min_usd, max_usd, string_search, account_id, group_ids, and categories filters.
  • Canonical connection-transaction objects gain transaction_id, usd_amount, and category.

​
Behavior changes

  • GET /v2/account-connections/transactions: pagination is now cursor-based (meta.next_cursor / ?cursor) instead of an unpaginated “recent activity” list.

​
v1.7.11: 15 July 2026

​
New account-connection providers

Data API:
  • octav: track DeFi protocol positions (lending, staking, LP, and more) across up to 20 EVM wallet addresses

​
New fields

  • GET /v2/accounts, GET /v2/accounts/{id}: AccountType gains defi (used by octav connections).
  • GET /v1/risk/alert-events: added alert_rule_id filter to narrow events to a specific alert rule.

​
Behavior changes

  • POST /v2/account-connections/{id}/transactions/sync is replaced by POST /v2/account-connections/transactions/sync: instead of syncing one connection synchronously, it now enqueues an async background job per connection across the whole workspace and returns immediately (202) with a batch id. No longer limited to Kraken — works for every persisted provider.
  • GET /v2/account-connections/{id}/transactions: now reads exclusively from persisted transaction history for every provider (previously fell back to a live provider fetch for non-persisted connections). Run the sync endpoint above first to populate history for a newly connected account.

​
v1.7.10: 14 July 2026

​
New account-connection providers

Data API:
  • binance: connect Binance accounts via API key and secret
  • okx: connect OKX accounts via API key, secret, and passphrase
  • bybit: connect Bybit accounts via API key and secret
  • bitget: connect Bitget accounts via API key, secret, and passphrase
  • gate: connect Gate.io accounts via APIv4 key and secret
  • kucoin: connect KuCoin accounts via API key, secret, and passphrase (optional api_key_version, defaults to 3)

​
New fields

  • GET /v2/account-connections, GET /v2/account-connections/{id}: Squads pending-proposal entries gain approved and rejected (arrays of signer pubkeys). Absent on connections persisted before this field existed, until their next refresh.

​
Behavior changes

  • POST /v1/risk/alert-rules: name is now required (previously optional).
  • PATCH /v1/risk/alert-rules/{rule_id}: name, if provided, must be non-empty.

​
v1.7.9: 8 July 2026

​
New account-connection providers

Data API:
  • anchorage: connect Anchorage-custodied wallets
  • dfns: connect Dfns-managed wallets (dfns_custody: organization or end_user)

​
New fields

  • GET /v2/accounts, GET /v2/accounts/{id}: AccountDto gains balances_usd (total USD value across balances, null when no asset has a known price) and balances_updated_at.
  • GET /v2/addresses/{address}/balances: each balance entry gains updated_at (omitted when never refreshed).
  • GET /v1/risk/alert-rules, GET /v1/risk/alert-rules/{rule_id}: AlertRuleDto gains alert_template, the full template the rule was created from (null if the template has since been removed).

​
Behavior changes

  • GET /v1/risk/alert-templates: response reshaped from a flat, cursor-paginated list of templates to groups, one entry per rule type with the networks and per-network template IDs it covers (groups[].templates[].template_id). The limit and cursor query params are removed; network/search_string/tags filtering still applies.

​
v1.7.8: 1 July 2026

​
New endpoints

Risk API — Alerting:
  • GET /v1/risk/channels, POST /v1/risk/channels, PUT /v1/risk/channels, GET /v1/risk/channels/{channel_id}, DELETE /v1/risk/channels/{channel_id}: manage alert delivery channels (Slack, Telegram, Discord, webhook, PagerDuty, email, Incident.io)
  • GET /v1/risk/alert-templates, GET /v1/risk/alert-templates/{template_id}: browse alert rule templates
  • GET /v1/risk/alert-rules, POST /v1/risk/alert-rules, GET /v1/risk/alert-rules/{rule_id}, PATCH /v1/risk/alert-rules/{rule_id}, DELETE /v1/risk/alert-rules/{rule_id}, PUT /v1/risk/alert-rules/{rule_id}/channels: create and manage workspace alert rules and their channel subscriptions
  • GET /v1/risk/alert-events, GET /v1/risk/alert-events/{event_id}: list and retrieve fired alert events

​
New account-connection providers

Data API:
  • cubist: connect Cubist-custodied wallets
  • privy: connect Privy-managed wallets

​
Enhanced parameters

  • GET /v2/account-connections/transactions: added tokens filter (comma-separated asset symbols, matched against each transaction’s displayed asset). size now caps the merged, newest-first result across all connections, rather than being applied to each connection independently.
  • GET /v2/account-connections/{id}/transactions: account_id must be the Range account UUID.

​
Behavior changes

  • Alert channels now report enabled (your on/off toggle) and connected (delivery readiness) separately. A Telegram channel is connected: false until its chat is linked; disabled channels are still returned by GET /v1/risk/channels (only deleted channels 404).
  • AlertRuleDto.parameters is now a flat object (e.g. { "threshold": 90 }) instead of an array of { field, value } pairs.

​
v1.2.0: 14 May 2026

​
New endpoints

Data API:
  • GET /v2/account-connections: List account connections
  • POST /v2/account-connections: Create an account connection
  • GET /v2/account-connections/{id}: Get account connection by ID
  • GET /v2/account-connections/{id}/status: Get connection status
  • DELETE /v2/account-connections/{id}: Delete an account connection
  • POST /v2/account-connections/plaid/link-token: Generate a Plaid link token
  • GET /v2/accounts: List accounts
  • GET /v2/accounts/{id}: Get account by ID
  • PUT /v2/accounts: Update accounts
  • GET /v2/groups: List groups
  • POST /v2/groups: Create a group
  • PUT /v2/groups/{id}: Update a group
  • DELETE /v2/groups/{id}: Delete a group

​
Enhanced parameters

  • GET /v2/transfers: added tx_hashes filter

​
v1.1.2: May 2026

​
New endpoints

Data API:
  • POST /v2/addresses/list: Store an address list
  • GET /v2/addresses/list/{hash}: Retrieve an address list
  • GET /v2/addresses/list/{hash}/balances: Balances for an address list
  • GET /v2/connections/byAddress: Address counterparties
  • GET /v2/connections/transfers: Transfers between two addresses
  • GET /v2/screening/addresses/{address}/risk: Address risk (auto-detect network)
  • GET /v2/screening/{network}/addresses/{address}/risk: Address risk (explicit network)
  • GET /v2/tokens/mints-burns: Token mint and burn events
  • GET /v2/tokens/summary: Token summary
  • GET /v2/tokens/top-holders: Top holders for a token
  • GET /v2/tokens/total-supply: Total supply for a token
  • GET /v2/transactions: List transactions
  • GET /v2/transactions/{id}: Get transaction by ID
  • GET /v2/transactions/by-network/{network}/{hash}: Get transaction by network and hash
  • GET /v2/transfers/top-assets: Top assets by transfer volume
  • GET /v2/transfers/top-networks: Top sender/receiver networks
Risk API:
  • POST /v1/simulate/solana/transactions: Batch simulate multiple Solana transactions

​
Enhanced parameters

  • GET /v1/address/balance: added network_type and token_contracts filters
  • GET /v2/addresses: added cursor and size for pagination
  • GET /v2/transfers: added address_list_hash and addresses filters

​
Deprecated endpoints

The following v1 endpoints have been removed in favor of v2 equivalents:
  • GET /v1/address/balances → use /v1/address/balance
  • GET /v1/network/relevant-cross-chain-transfers → use /v2/transfers
  • GET /v1/network/transactions/errors
  • GET /v1/network/transfers → use /v2/transfers
  • POST /v1/protocols/transactions → use /v2/transactions
  • GET /v1/protocols/transactions/{hash} → use /v2/transactions/by-network/{network}/{hash}

​
v1.1.1: November 2025

  • Documentation restructure with dedicated tabs for Data, Risk, and Faraday APIs
  • Expanded cross-chain coverage to 100+ networks
  • Enhanced address labeling with entity recognition

​
v1.0: March 2025

  • Initial release of Data API and Risk API
  • Core blockchain data endpoints across 18+ networks
  • Address risk scoring with proximity analysis
Last modified on August 4, 2026