API Keys
All requests to the/v1/extract endpoint require authentication using an API key.
Getting an API Key
- Join the waitlist
- Once approved, you’ll receive your API key via email
pk_ followed by a unique identifier.
Using Your API Key
Bearer Token (Recommended)
Include your API key in theAuthorization header as a Bearer token:
SDK Configuration
- Python
- JavaScript
Option 1: Environment Variable (Recommended)Option 2: Direct Configuration
Authentication Errors
401 Unauthorized
Returned when authentication fails:- Missing
Authorizationheader - Invalid API key format
- Revoked or expired API key
- Typo in the API key
403 Forbidden
Returned for the playground endpoint when the request origin is not allowed:Playground (No Auth)
The/v1/playground endpoint allows testing without an API key, but with restrictions:
- Rate Limited: 10 credits per day per IP
- Origin Restricted: Only allowed from authorized domains
The playground is designed for testing and demos. For production use, always use an API key with the
/v1/extract endpoint.Security Best Practices
Use Environment Variables
Never hardcode API keys. Use environment variables or secrets managers.
Server-Side Only
Make API calls from your backend. Never expose keys in frontend code.
Rotate Regularly
Periodically rotate your API keys, especially if you suspect a leak.
Principle of Least Privilege
Use separate keys for development and production environments.
