Set up API keys, manage tokens, and configure secure access to the Grader.io REST API.
Secure API access is essential for protecting your lead data and ensuring only authorized systems can interact with your graders. This guide covers authentication methods, token management, and security best practices.
Include your API key in the Authorization header:
curl -H "Authorization: Bearer sk_live_abc123xyz789" \ -H "Content-Type: application/json" \ https://api.grader.io/v1/submissions
| Key Type | Prefix | Permissions | Use Case |
|---|---|---|---|
| Live | | Full access | Production applications |
| Test | | Sandbox only | Development and testing |
| Read-only | | GET requests only | Analytics and reporting |
# Store in environment variables export GRADER_API_KEY="sk_live_your_key_here" # Use in applications curl -H "Authorization: Bearer $GRADER_API_KEY" ...
API requests are limited by plan:
| Plan | Requests/minute | Daily limit |
|---|---|---|
| Starter | 60 | 5,000 |
| Pro | 300 | 25,000 |
| Elite | 1,200 | 100,000 |
| Enterprise | Custom | Custom |
// 401 Unauthorized - Invalid key { "error": "unauthorized", "message": "Invalid API key" } // 403 Forbidden - Insufficient permissions { "error": "forbidden", "message": "Read-only key cannot create submissions" } // 429 Rate Limited { "error": "rate_limit_exceeded", "message": "Too many requests", "retry_after": 60 }