Overview
Request Network API supports two authentication modes:x-api-keyfor server-side integrationsx-client-idfor browser/client integrations (withOriginheader)
Choose the Right Method
| Method | Best for | Header(s) |
|---|---|---|
| API Key | Backend services, cron jobs, trusted server environments | x-api-key |
| Client ID | Browser/front-end calls where client auth is required | x-client-id (+ Origin) |
API Key Authentication
Use API keys for backend calls.Example
cURL
Client ID Authentication
Use Client ID when your integration needs browser-side authentication flow.Example
cURL
For browser-based requests,
Origin is part of the request context and is required for Client ID auth.Header Reference
x-api-key: API key used for server-side authx-client-id: Client identifier used for client-side authOrigin: required with Client ID flows in browser contexts
Common Authentication Errors
401 Unauthorized
- Missing auth header
- Invalid/expired API key or client ID
403 Forbidden
- Credentials are valid but not allowed for the requested operation
- Client ID is revoked or restricted
429 Too Many Requests
- Request rate exceeded for your credentials
Security Guidance
- Keep API keys server-side and out of frontend bundles
- Store credentials in environment variables or secret managers
- Rotate compromised credentials immediately
- Verify webhook signatures independently (webhook signing uses a separate secret)
Related Pages
API Portal
Create credentials and manage webhook configuration.
Webhooks
Signature verification and delivery behavior.
OpenAPI Reference
Full endpoint authentication requirements.