Oydin for developers

Authentication

Two ways in: a browser session for the Oydin app, and personal API tokens for your code.

Personal tokens

Tokens look like oyd_… and belong to one business. Send them as a bearer header on every /api/v1/* request:

Authorization: Bearer oyd_XXXXXXXX

Only a SHA-256 hash and an 8-character prefix are stored, so a lost token cannot be recovered. Create a new one and revoke the old one.

Scopes

ScopeAllows
readAll GET /api/v1/* endpoints.
writePOST /api/v1/transactions/. Add it alongside read.

Rate limit

60 requests per minute per token. Beyond that you get 429 {"error":"rate_limited"} and a Retry-After header in seconds.

Errors

StatuserrorMeaning
401invalid_tokenMissing, malformed or revoked token.
403forbiddenToken lacks the needed scope.
429rate_limitedWait Retry-After seconds.

Auth for your own services

REST handlers and MCP servers you connect to Oydin use one custom header (for example Authorization: Bearer … or X-Api-Key: …). Its value is encrypted at rest and is never returned by the API.