Authentication Overview
All Vantio API endpoints require authentication using a Bearer token. Your API key should be included in the Authorization header of every request.
Getting Your API Key
- Log in to your Vantio Dashboard
- Navigate to Settings → API Keys
- Create a new API key or copy an existing one
- Your API key starts with
sk_
Never expose your API key in client-side code, commit it to version control, or share it publicly. Treat it like a password.
Include your API key in the Authorization header:
Making API Requests
Using cURL
Using JavaScript (Fetch API)
Using JavaScript (Axios)
Using Python (Requests)
Request Methods
The Vantio API uses standard HTTP methods:
Request Body Format
For POST and PUT requests, send JSON data in the request body:
Query Parameters
Many endpoints support query parameters for filtering and pagination:
All successful API responses return JSON:
Error Responses
The API uses standard HTTP status codes:
200 - Success
400 - Bad Request (invalid parameters)
401 - Unauthorized (invalid or missing API key)
404 - Not Found (resource doesn’t exist)
Error responses include a message:
Handling Errors
Always check the response status and handle errors appropriately:
Rate Limits
The Vantio API enforces rate limits to ensure fair usage. Check response headers for rate limit information:
X-RateLimit-Limit - Maximum requests allowed
X-RateLimit-Remaining - Remaining requests in current window
X-RateLimit-Reset - Time when the rate limit resets
Best Practices
- Store API keys securely - Use environment variables, never hardcode
- Handle errors gracefully - Always check response status codes
- Use idempotency keys - For POST requests that might be retried
- Implement retry logic - For transient failures (with exponential backoff)
- Cache responses - When appropriate to reduce API calls
Environment Variables
Store your API key as an environment variable: