Documentation Index
Fetch the complete documentation index at: https://docs.vepler.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The Vepler API uses API key authentication for all requests. You must include your API key in thex-api-key header of every request.
Keep your API keys secure! Never expose them in client-side code or public repositories.
Obtaining API Keys
Create Account
Sign up at app.vepler.com
Making Authenticated Requests
Include your API key in thex-api-key header:
API Key Format
API keys use the prefixvpr_live_ followed by a unique identifier:
Security Best Practices
Environment Variables
Environment Variables
Never hardcode API keys. Use environment variables:
.env
Key Rotation
Key Rotation
Rotate your API keys regularly:
- Generate a new key in the dashboard
- Update your application with the new key
- Verify the new key works
- Delete the old key from the dashboard
Server-Side Only
Server-Side Only
Always make API calls from your server, never from client-side code. Your API key should never be exposed in browser JavaScript, mobile apps, or public repositories.
Error Handling
Handle authentication errors gracefully:Authentication Errors
| Status Code | Description | Solution |
|---|---|---|
401 | Invalid or missing API key | Check your API key is correct and included in the x-api-key header |
403 | Insufficient permissions | Your API key does not have access to this resource |
Testing Authentication
Verify your setup with a health check endpoint:Next Steps
Quick Start
Build your first integration
API Reference
Explore all endpoints
TypeScript SDK
Use the official SDK
Error Handling
Handle errors effectively