Example Prompts
Example Prompts
See Example prompts for component-specific prompts.
Code Examples
Code Examples
Jump to Code Examples for ready-to-use snippets.
Dashboard Prompt
Dashboard Prompt
Copy the Complete Dashboard Prompt to generate a full dashboard.
Prerequisites
- v0 account (Vercel v0)
- Wallbit API key from your dashboard
Project context
When using v0 to generate components that interact with the Wallbit API, include context about the API in your prompts. Here’s what v0 should know:API Overview
Wallbit is a global neobank and the world’s first to offer a public API for programmatic account control. We offer US accounts, investments in ETFs, stocks and bonds, and local currency rails. The API allows you to:- Query account balances (checking and investment)
- View transaction history
- Execute trades (buy/sell stocks, ETFs, bonds)
- Get bank account details for deposits (ACH/SEPA)
- Retrieve crypto wallet addresses
Authentication
All requests require anX-API-Key header:
Available Endpoints
Balance
GET /api/public/v1/balance/checking- Get checking account balanceGET /api/public/v1/balance/stocks- Get investment portfolio
Transactions
GET /api/public/v1/transactions- List transactions with filters
Trades
POST /api/public/v1/trades- Execute a buy/sell trade
Account Details
GET /api/public/v1/account-details- Get bank account details (ACH/SEPA)
Wallets
GET /api/public/v1/wallets- Get crypto wallet addresses
Assets
GET /api/public/v1/assets- List available assetsGET /api/public/v1/assets/{symbol}- Get asset details
Operations
POST /api/public/v1/operations/internal- Move funds between accounts
Using v0 with Wallbit API
Example prompts
When generating components, include API context in your prompts: Example 1: Balance display componentCode Examples
Fetch balance
Execute a trade
List transactions with filters
Error Handling
Always handle these HTTP status codes:401- Invalid or missing API key403- Insufficient permissions412- KYC incomplete or account locked422- Validation error429- Rate limit exceeded
Best Practices for v0 Prompts
- Include API endpoint details: Specify the exact endpoint and method (GET/POST)
- Mention authentication: Always note that
X-API-Keyheader is required - Specify data structure: Describe the expected request/response format
- Request error handling: Ask for proper error state handling
- Use environment variables: Request that API keys be stored in env vars
- Include loading states: Ask for loading indicators during API calls

