Information
- License: AGPL-3.0-or-later
- OpenAPI version:
3.1.0
Merran documentation /API & integrations
Everything the Merran app does, it does through this API: the same routes are open to scripts and to tools like Home Assistant. Tools use an API key: make one at POST /api/auth/api-keys while signed in, then send it as Authorization: Bearer mrn_…. Each route a key can use says which permission it needs, in x-merran-permission (like recipes:read); routes without it refuse keys. Browsers sign in with POST /api/auth/sign-in/username and send the session cookie it sets.
Information
3.1.0The cookie that signing in sets.
Security scheme type: apiKey
Cookie parameter name: merran.session_token
An API key, made at POST /api/auth/api-keys, sent as Authorization: Bearer mrn_…. It acts as its person in one household, with only the permissions it was given.
Security scheme type: http
Bearer format: mrn_…
© 2026 Kyle Johnson. Documentation: CC BY 4.0. Merran: AGPL-3.0-or-later.