Learn how to authenticate your API requests
The Reap Automation API uses API key authentication. You’ll need to include your API key in the Authorization
header of every request.
Keep your API key secure! Don’t commit it to version control or share it publicly. Store it in environment variables or a secure configuration management system.
Include your API key in the Authorization
header with the Bearer
prefix:
Header | Value | Required |
---|---|---|
Authorization | Bearer YOUR_API_KEY | Yes |
Content-Type | application/json | Yes |
Store your API key in environment variables rather than hardcoding it in your application.
Rotate your API keys regularly for enhanced security.
Use separate API keys for different environments (development, staging, production).
Monitor your API key usage to detect any unauthorized access.
API keys do not expire by default. You can:
To revoke an API key:
Revoking an API key immediately invalidates all requests using that key. Make sure to update your applications before revoking keys.
All API requests are subject to rate limiting:
429 Too Many Requests
errorHeader | Description |
---|---|
X-RateLimit-Limit | Maximum requests per minute |
X-RateLimit-Remaining | Remaining requests in current window |
X-RateLimit-Reset | Time when rate limit resets (Unix timestamp) |
Status Code | Error | Description |
---|---|---|
401 | Unauthorized | Missing or invalid API key |
403 | Forbidden | API key doesn’t have required permissions |
429 | Too Many Requests | Rate limit exceeded |
Test your API key with a simple request to get your presets:
A successful response indicates your authentication is working correctly.