Changelog

Separate access to activity - Reading activity in Platform API v2 requires api:activity:read. Transaction lists and details continue to use api:transaction:read. Existing keys retained their activity access when this permission was introduced; new keys select the two permissions separately. See Permissions.

Management-key permissions - Management keys can create and revoke API/RPC keys within their assigned permissions. Listing, reading, creating or revoking Management keys requires a user session with the appropriate workspace permissions.

Cancellation based on recorded payments - An open or processing invoice can be cancelled when none of its recorded valid payments is awaiting confirmation and the confirmed amount is below the requested amount. A confirmed partial payment does not prevent cancellation. An unmet cancellation condition returns 422 rather than an internal server error.

Payment links after cancellation - No new payments are linked to a cancelled invoice, including payments discovered later with an earlier block time. Existing links remain, and the address can be reused for another invoice. See Cancel an invoice.

Payment windows and confirmations - Invoice payment matching takes the block's timestamp into account. After the payment window ends, processing keeps pending checks and confirmations distinct from a completed invoice. Received and confirmed amounts remain separate. See Invoice lifecycle.

EVM address matching - EVM addresses are normalized when supplied to the API, so letter case does not prevent matching an address to its recorded data.

Version 1 payload compatibility - Channels with payload_version: v1 retain the earlier chain and asset identifiers. Webhook payload versions remain independent of the Platform API version. See Webhooks.

Workspace access and keys - VKS has a workspace-scoped key with vks:access. Authorized users manage member access in the dashboard; related changes appear in the workspace audit history. See VKS permissions.

Quota responses - Platform API v2 and Management return structured 429 responses for resource quotas and action limits. Error codes distinguish quota exhaustion from action-rate limits; recovery depends on the reported limit. See Rate limits and quotas.

Idempotency keys - Mutations in Platform API v2, Management and VKS use Idempotency-Key to identify an operation. Keep the same key and request when retrying an unknown outcome; a new key represents a new intent. Replay windows and recovery steps are described in Idempotency.

Normalized blockchain data - Transactions use chain_gid, txid and family-specific details; decoded events and per-address activity share the current Platform data model. See Events.

Balances by chain family - Search and summarize balances within a selected family. is_sync describes freshness; an unknown amount is absent rather than zero. See Tokens and balances.

Subscription triggers - Choose block, network or Bitcoin mempool for each subscription. Trigger choice, filtering and reorganization handling are described in Events.

Delivery history and recovery - Notification history includes delivery attempts and manual resend outcomes. Channels expose their enabled state and retry budget. See Notification channels.

Token catalog and trust - Token metadata distinguishes catalog support, shared verification and project trust. See Tokens and balances.

Invoice reconciliation - Invoice lifecycle and received/confirmed amounts are separate facts. See Invoices for partial payments, cancellation and the public view.

Network coverage - 7 networks provide full monitoring; Solana supports addresses and the token catalog. See the network matrix for capabilities by product.

EVM simulation - Preview calls, decoded events, balance effects and execution errors without broadcasting. See Transaction simulation.

Rebuilt information architecture - Get Started, Guides and API Reference are now three focused sections, each with its own sidebar and built-in previous/next navigation.

New navigation - a mega-menu across the top and an All guides index so you can find any guide at a glance.

Every guide redesigned - integration patterns, events, notification channels, invoices, transaction simulation and AI integration now lead with visual, scannable layouts.

API Reference refreshed - Authentication, Permissions, Errors and Standards rewritten with clearer examples and a consistent layout.

Brand refresh - new colors, typography and components throughout, with full English and Russian across the site.

Versioned reference - v2 is the default, and /v1 stays available at /apis/platform/v1 with a version picker in the sidebar.

A reimagined homepage - a clearer introduction to what Vilna does, with an animated sample API preview.

Interactive quickstart - explore a fixed sample request and response, then use the guides and reference to make a request from your own terminal. The sample does not send a request or validate credentials.

Redesigned interface - manage workspaces, projects, API keys and members from a cleaner, faster dashboard.

Reworked navigation matched to the new brand, with light and dark themes.

Core resources - the first set of REST resources: public keys, addresses, transactions, balances, tokens and notification channels, with consistent pagination.

EVM simulation - preview an EVM call's outcome before broadcasting it.

API-key authentication and rate limits - every call is authenticated and rate-limited.

A documentation site - the first version of docs.vilna.io, with an interactive API reference.

English and Russian - full bilingual coverage across the docs.

OpenAPI 3.1 spec - the contract published as a machine-readable spec.

CAIP and BIP-44 standards - CAIP-2, CAIP-10 and CAIP-19 for chain and asset identifiers, BIP-44 for derivation paths.

Webhooks with retries - a failed delivery retries automatically.

Transaction and transfer monitoring - track transactions and transfers as they happen on chain.

HD wallets - wallet generation from an extended public key, derived by BIP-44.

Webhooks and email - notifications for blockchain events, delivered as webhooks or email.

Access by request - through support@vilna.io.