API Reference
Versioned REST endpoints for Hydra workspace data — leads, contacts, accounts, conversations, tickets. Bearer-authed with the same keys as the dashboard, rate-limited at 60 requests per minute, ready for any integration that speaks REST.
Authentication
Mint a key in the dashboard at Settings → API Access. Send it as a Bearer token on every request:
curl -H "Authorization: Bearer hmcp_..." \
https://app.hydra-help.com/api/v1/leadsRate limit
60 requests per key per minute, sliding window. Successful responses include X-RateLimit-Remaining; over-limit returns 429 with Retry-After seconds.
Error envelope
Errors share { error, code }. Branch on the stable code field — unauthorized, forbidden_scope, validation_error, not_found, rate_limited, fk_blocked, server_error.
How this differs from MCP
Hydra also exposes /api/mcp/v1/* for AI tool callers (Claude, custom MCP clients) — same keys, two-step preview/confirm writes for LLM-tool safety. The public REST API at /api/v1/* is the right shape for Zapier / n8n / partner backends.