Skip to Content
APIAPI Versioning

API Versioning

Hatcher uses URL-based API versioning to ensure stability for integrations.

Current Version

v1 — All programmatic API endpoints are available under /api/v1/.

https://api.hatcher.host/api/v1/agents https://api.hatcher.host/api/v1/me https://api.hatcher.host/api/v1/usage

Version Headers

Every response from /api/v1/* includes these headers:

HeaderValueDescription
API-Versionv1Current API version
X-API-Version1Numeric version for programmatic checks
X-RateLimit-LimitnumberDaily request limit
X-RateLimit-RemainingnumberRequests remaining today
X-RateLimit-ResettimestampUnix timestamp when limit resets

Future Deprecation Headers

When a new version launches, deprecated versions will include:

HeaderExampleDescription
DeprecationtrueIndicates this version is deprecated
Sunset2027-01-01T00:00:00ZDate when this version will be removed

Authentication

All /api/v1 endpoints require authentication via:

  • JWT Token — Authorization: Bearer <jwt> (from /auth/login)
  • API Key — Authorization: Bearer hk_<key> (from Dashboard Settings)

Available Endpoints

MethodPathDescriptionRate Limit
GET/api/v1/meCurrent user info30/min
GET/api/v1/usageAPI usage stats30/min
GET/api/v1/agentsList your agents30/min
GET/api/v1/agents/:idAgent details30/min
GET/api/v1/agents/:id/statusAgent status60/min
POST/api/v1/agents/:id/chatSend message10/min
POST/api/v1/agents/:id/startStart agent5/min
POST/api/v1/agents/:id/stopStop agent5/min
POST/api/v1/agents/:id/restartRestart agent5/min

Internal Endpoints

Internal endpoints (/internal/*, /health, /healthz) are not versioned and will never be prefixed. These are for platform infrastructure only.

Versioning Policy

  1. No breaking changes within a version — fields may be added but never removed
  2. 6-month deprecation window — deprecated versions include Deprecation and Sunset headers
  3. Migration guides — published with each new version
  4. Semantic versioning — major version bumps for breaking changes only