API Authentication
Our API uses two required headers for authentication and versioning. Both headers must be included in every request to ensure proper authentication and API version handling.
Required Headers
X-Api-Token
Your unique API token for authentication
Yes
X-Api-Version
The API version you want to use (currently only v1
)
Yes
Getting Your API Token
Access your application dashboard
Navigate to the API settings section
Copy your unique API token
Keep this token secure and don't share it publicly
Making Authenticated Requests
Example Request
Using Different Programming Languages
Python
JavaScript
Ruby
Common Authentication Errors
401 Unauthorized
This error occurs when:
The
X-Api-Token
header is missing or invalidThe
X-Api-Version
header is missing or invalid
Example error response:
Best Practices
Keep Your Token Secure
Never share your API token publicly
Don't commit your token to version control
Use environment variables to store your token
Rotate your token if it's been compromised
Version Management
Always specify the API version using
X-Api-Version
Currently supported versions:
v1
: Current stable version
Error Handling
Implement proper error handling for authentication failures
Include retry logic with appropriate backoff for network issues
Log authentication errors for debugging purposes
Rate Limiting
To protect our API from abuse, we implement rate limiting. If you exceed the rate limit, you'll receive a 429 Too Many Requests
response. Please contact our support team if you need increased rate limits for your application.
Support
Last updated