Vertigo RPC Playground

Parameter Types:

• Named Parameters: Use JSON object format {"param": "value"}
• Addresses: Base58-encoded Solana addresses (32 bytes)
• Slots: Solana slot numbers (integers)
• Timestamps: Unix timestamps in seconds (e.g., 1704067200)
• Pagination: Use offset and limit for paging

Analytics Methods:

• Slot-based: Use start_slot/end_slot for efficient queries
• Time-based: Use start_time/end_time (includes block_time)
• Filtering: All filters are optional
• Performance: Slot-based queries are faster than time-based

Common Patterns:

• Set null values for optional parameters
• Use limit=10 for testing, up to 1000 for production
• Analytics tables are optimized for time-series queries
• All methods support pagination with offset/limit

Sorting (getPools):

• Available fields: volume_24h, created_at, last_trade, trades_24h, fees_24h
• Syntax: "field:direction" (e.g., "volume_24h:desc")
• Directions: asc (ascending) or desc (descending, default)
• Multiple sorts: comma-separated (e.g., "volume_24h:desc,created_at:asc")
• Example: {"sort": "volume_24h:desc"}

Authentication: All requests require either:

• API Key: In the X-API-Key header
• JWT Token: In the Authorization header as "Bearer <token>"

Use the authenticate method to exchange your API key for a JWT token. JWT tokens have different expiration times based on access level.

WebSocket Event Subscription:

• Authentication: First authenticate with your API key to get a JWT token
• Connection: Connect to WebSocket endpoint on port+1 (e.g., 8081)
• Subscription: Send subscribe_events with JWT token and filters
• Filters: All events, by mint, or by pool

Event Types:

• Swap: Token swap events
• Claim: Fee claim events
• Create: Pool creation events
• Update: Pool update events

Event Data:

• Pool address
• Mint addresses (optional)
• User address
• Amount and fee information
• Slot and signature