Overview
QrX offers two tiers of access: Public (unauthenticated) and Authenticated (with API key). Authentication is optional but recommended for production use.Rate Limits
- Public Access
- Authenticated Access
No API Key Required
Perfect for testing and low-volume use cases.- Rate Limit: 10 requests per minute
- Authentication: None required
- Use Cases: Testing, prototyping, personal projects
Getting Your API Key
Follow these steps to obtain your API key:1
Access Dashboard
Navigate to the QrX Dashboard
2
Sign In
Create an account or sign in if you already have one
3
Generate Key
Your API key will be displayed on the dashboard. Copy it to a secure location.
4
Test Your Key
Make a test request to verify your API key works correctly
Authentication Methods
QrX supports two methods for providing your API key:Method 1: Query Parameter
Include the API key as a query parameter in the URL:- Simple to implement
- Works everywhere
- API key may appear in logs
- Visible in browser history
Method 2: HTTP Header (Recommended)
Include the API key in thex-api-key header:
- ✅ More secure
- ✅ Doesn’t appear in URLs
- ✅ Not logged by many servers
- ✅ Industry best practice
- Slightly more complex to implement
Code Examples
JavaScript/Fetch
Python
Node.js (Axios)
Rate Limit Responses
When you exceed the rate limit, you’ll receive: HTTP Status:429 Too Many Requests
Response: Error message indicating rate limit exceeded
Rate limits reset on a rolling window basis. Wait a minute and try again, or upgrade to an authenticated tier for higher limits.
Best Practices
Secure StorageStore API keys in environment variables, never in code.
Key RotationRotate keys periodically and if they’re compromised.
Monitor UsageTrack your API usage through the dashboard.
Use HeadersPrefer header authentication over query parameters.