Skip to main content
Use v0 to generate UI components that integrate with the Wallbit API. This guide shows how to configure v0 for better results when building interfaces for Wallbit API integrations.
See Example prompts for component-specific prompts.
Jump to Code Examples for ready-to-use snippets.
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 an X-API-Key header:

Available Endpoints

Balance

  • GET /api/public/v1/balance/checking - Get checking account balance
  • GET /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 assets
  • GET /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 component
Example 2: Transaction list component
Example 3: Trade execution form

Code Examples

Fetch balance

Execute a trade

List transactions with filters

Error Handling

Always handle these HTTP status codes:
  • 401 - Invalid or missing API key
  • 403 - Insufficient permissions
  • 412 - KYC incomplete or account locked
  • 422 - Validation error
  • 429 - 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-Key header 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

Example Component Structure

When generating components, v0 should create:

Complete Dashboard Prompt

Copy and paste this prompt to v0 to generate a complete Wallbit account dashboard:

Useful Cards

API Reference

Complete documentation for all Wallbit API endpoints.

Get API Key

Create your API key in the Wallbit dashboard.