> ## Documentation Index
> Fetch the complete documentation index at: https://docs.range.org/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> API changes and updates to Range Data API and Risk API.

## 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