REST API
Odyhook exposes a public REST API at /api/v1 for managing sources, destinations, routes, and events programmatically.
Authentication
Every request authenticates with an ody_ API token in the Authorization header. Mint one at Settings → API Tokens:
curl -H "Authorization: Bearer ody_…" https://odyhook.dev/api/v1/sourcesRequests without a valid token are rejected with 401.
Resources
| Resource | Collection (/api/v1/…) | Item (/api/v1/…/{id}) |
|---|---|---|
| Sources | GET list, POST create | GET get, PATCH update, DELETE |
| Destinations | GET list, POST create | GET get, PATCH update, DELETE |
| Routes | GET list, POST create | GET get, PATCH update, DELETE |
| Events | GET list | GET get |
| Event search | POST /api/v1/events/search | — |
| Fixtures | POST /api/v1/fixtures | — |
Events are read-only over the API — they enter the system through the ingest endpoint (/api/ingest/<slug>), not by POSTing to /api/v1/events.
List endpoints use cursor pagination: each response includes a nextCursor, which you pass back as the cursor query parameter to fetch the next page.
OpenAPI
A machine-readable OpenAPI specification is served at /openapi.json. Point your client generator or API explorer at it to get typed bindings for every endpoint above.
For a browsable, human-readable reference of every endpoint and schema, see the API reference.