Elonn Docs Platform Documentation

api

api.elonn.local is the shared identity authority for Elonn. Production is api.elonn.com.

This service owns authentication, identity sessions, and the member directory. All other services validate identity through API endpoints and must not connect directly to the elonn_api database.

Owns

  • member identity records
  • auth tokens (elonn_api_token cookie)
  • account credential validation for CalDAV clients
  • member directory

Role in the stack

  1. elonn.local posts login and registration requests here
  2. web.elonn.local validates the shared auth cookie through /identity/me
  3. world.elonn.local, time.elonn.local, social.elonn.local, and admin.elonn.local validate identity through API endpoints
  4. world.elonn.local, messages.elonn.local, and social.elonn.local use /identity/members for member selection, open Message recipient lookup, and Social DM recipient lookup

Routes

POST /identity/register
POST /identity/login
GET  /identity/me
GET  /identity/members
POST /identity/logout
POST /identity/dav/validate
GET  /admin/members
POST /admin/members/update
GET  /health
GET  /ready

Key configuration

Key Purpose
ELONN_API_BASE_URL Used by all consuming services to locate this service
ADMIN_ALLOWED_EMAILS Comma-separated operator allowlist for admin routes

Canonical terms

  • member — a person with a registered account
  • token — credential issued after authentication
  • session — always qualify: auth session