System and service status operations
Vilna API (1.0.0)
Welcome to the Vilna API Reference. This is the complete OpenAPI specification for all API endpoints.
Quick Links
- API Overview - Introduction and concepts
- Security Guide - Authentication and webhook verification
- CAIP Standards - Asset identification standards
- Quick Start Guide - Step-by-step integration tutorial
API Endpoints
Asset Management
- Assets - Discover and manage digital assets
Address Operations
- Addresses - Manage blockchain addresses
- Extended Public Keys - HD wallet management
Monitoring and Notifications
- Transactions - Transaction monitoring
System
- Blockchains - Information on supported blockchains
- System Status - Health checks and version info
Need Help?
Visit our documentation portal for detailed guides and examples.
Field to sort results by. Use "-" prefix for descending order
Filter transactions by initiator addresses (exact match)
Filter transactions by target addresses (exact match)
Filter transactions where any of the addresses is either initiator or target address
Filter transactions by blockchain chain GIDs
- Mock serverhttps://docs.vilna.io/_mock/apis/spec/transactions
- Production environmenthttps://demo.vilna.app/v1/transactions
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.vilna.io/_mock/apis/spec/transactions?limit=20&page=1&sort_by=-created_at&initiator_address=0x742d35Cc6b3C0532925a3b8c17c8b4842f6c8E5a%2C0x123456789abcdef123456789abcdef123456789ab&target_address=0xdAC17F958D2ee523a2206206994597C13D831ec7%2C0x9876543210abcdef9876543210abcdef98765432&address=0x742d35Cc6b3C0532925a3b8c17c8b4842f6c8E5a%2C0xdAC17F958D2ee523a2206206994597C13D831ec7&chain_gids=eip155%3A1%2Ceip155%3A56%2Ceip155%3A137&is_success=true' \
-H 'X-Api-Key: YOUR_API_KEY_HERE'Successful response returning a list of blockchain transactions
List of blockchain transactions with their asset transfers
Hash of the transaction on the blockchain
Blockchain identifier according to CAIP-2.
The chain_gid is a case-sensitive string uniquely identifying a blockchain. It is composed of:
- namespace — a short identifier describing an ecosystem or standard (e.g.
eip155,cosmos) - reference — an identifier for a specific blockchain within that namespace
Syntax
chain_id = namespace ":" reference
namespace = [-a-z0-9]{3,8}
reference = [-_a-zA-Z0-9]{1,32}Examples
eip155:1— Ethereum mainneteip155:56— Binance Smart Chaincosmos:cosmoshub-4— Cosmos Hub mainnetbip122:000000000019d6689c085ae165831e93— Bitcoin mainnet
Chain family that identifies blockchain ecosystems united by common protocol or account model.
Available families:
evm: Ethereum Virtual Machine-based blockchainsbitcoin: Bitcoin and Bitcoin-compatible networkssolana: Solana blockchain ecosystemtron: Tron blockchain ecosystem
The chain family is used to determine which blockchain ecosystem the address belongs to and how it should be generated or validated.
Reference to a blockchain address with minimal system context
A blockchain address in its native format. This is a generic schema for any blockchain address, including addresses, smart contract addresses, and token contract addresses.
The actual format depends on the blockchain network:
EVM chains (Ethereum, BSC, Polygon, etc.): 0x followed by 40 hexadecimal characters
- Example:
0x8521E8b15eCEF4D4269Fded3E6694225E096959E
- Example:
Bitcoin: Various formats depending on address type
- P2PKH (Legacy): Starts with 1, Example:
1GxHzNEymq1MLhxpdWAMJLN1UusYJ2Sy45 - P2SH (Wrapped SegWit): Starts with 3, Example:
3Do92Dmff87UuY9Yiu2iFG2Kj9bpRaeJSF - P2WPKH (Native SegWit): Starts with bc1, Example:
bc1q8faxe8g4u2v67qfwf9d8xhyl5tkkkphvet6r08
- P2PKH (Legacy): Starts with 1, Example:
Solana: Base58 encoded, 32-44 characters
- Example:
5EYCAe5ijiHbZBU14TyKHADUrkaAfc4ZyTXKRVKp49F8
- Example:
Tron: Base58 encoded addresses starting with T
- Example:
TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
- Example:
Cosmos ecosystem: Bech32 format with chain-specific prefix
- Example:
cosmos1vx8knpllrj7n963p9ttd80w47kpacrhuts497x
- Example:
This schema is intentionally generic to support addresses from any blockchain. The specific validation rules depend on the blockchain network and address type.
Collection of asset transfers within this transaction (e.g., ERC-20, ETH, BTC outputs, Solana SPL tokens). Always contains at least one transfer.
Asset identifier in CAIP-19 format. Identifies a asset across blockchains. Format: <chain_gid>/<asset_namespace>:<asset_reference> Examples: - Ethereum ETH: eip155:1/slip44:60 - Ethereum USDT ERC-20: eip155:1/erc20:0xdAC17F958D2ee523a2206206994597C13D831ec7
Sequential index of the transfer within the transaction, starting from 0. Defines order of transfers and ensures uniqueness per transaction.
Type of asset transfer within a blockchain transaction
Reference to a blockchain address with minimal system context
Reference to a blockchain address with minimal system context
Amount transferred in the smallest unit of the asset (without decimal adjustment)
Additional blockchain-specific metadata for the transfer. The structure varies based on the blockchain's technical requirements and available transaction data. This field contains essential metadata that helps identify and process transfers within the context of their respective blockchain ecosystems.
Metadata specific to EVM (Ethereum Virtual Machine) blockchain transfers.
Timestamp when the resource was created
{ "items": [ { … }, { … }, { … }, { … } ], "meta": { "page": 1, "limit": 20, "total": 4, "total_pages": 1 } }