Skip to main content

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

  1. Log in to your Vantio Dashboard
  2. Navigate to Settings → API Keys
  3. Create a new API key or copy an existing one
  4. 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.

Authentication Header

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:

Response Format

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

  1. Store API keys securely - Use environment variables, never hardcode
  2. Handle errors gracefully - Always check response status codes
  3. Use idempotency keys - For POST requests that might be retried
  4. Implement retry logic - For transient failures (with exponential backoff)
  5. Cache responses - When appropriate to reduce API calls

Environment Variables

Store your API key as an environment variable: