Feather uses organization-scoped API keys for server-to-server requests. Send your key in the X-API-Key header on every authenticated API call.
Get an API Key
- Open the Feather dashboard.
- Go to your organization settings.
- Create an API key for the integration or environment you are setting up.
- Store it in your secret manager or deployment platform.
Treat Feather API keys like production credentials. Store them in environment variables or a secrets manager, never in client-side code.
Send Your First Authenticated Request
curl "https://prod.featherhq.com/api/v1/organization" \
-H "X-API-Key: $FEATHER_API_KEY"
X-API-Key: your_api_key_here
Bearer.
Best Practices
- Create different keys for local development, staging, and production.
- Rotate keys when ownership changes or exposure is suspected.
- Keep keys in backend services only.
- Log request IDs and response codes, not secrets.
What Uses API Keys?
API keys cover the main management and automation APIs, including:
- Agents and deployments
- Direct dispatch and workflows
- Phone number setup
- SMS, email, and chat thread creation
- Tools, knowledge base, calendars, and reports
Some public-facing flows such as shared sessions or web chat use short-lived tokens generated by Feather after your authenticated setup request.
Next Steps
