Authentication
How HappyHorse secures API access.
API Key Authentication
HappyHorse uses bearer token authentication.
Authorization: Bearer YOUR_API_KEYEnvironments
production: enabled only for approved accountsstaging: available for integration testing when explicitly granted
Best Practices
- keep one key per environment
- rotate keys when a teammate leaves
- never expose keys in client-side code
- log request ids, not secrets
Failed Authentication
Requests fail with 401 when:
- the key is missing
- the key is invalid
- the key is valid but not enabled for the requested workflow
See Errors for response examples.
HappyHorse API Docs