Welcome to the Medera API Reference

The Medera API is split across two services that share authentication, tenant context, and audit infrastructure.

Backend

Tenant + PHI persistence, workflow + deployment lifecycle, EHR + billing integration, real-time channel.

AI Services

Multimodal engines, Neurobehavioral Construct, Care Orchestrator, Medera Voice, clinical NLP.

In production the public host is api.medera.info and routes to both services through the API gateway.

Base URLs

Environment	Backend host	AI Services host
Production	`https://api.medera.info`	`https://api.medera.info` (proxied)
Staging	`https://staging.api.medera.info`	`https://staging.api.medera.info`
Sandbox	`https://sandbox.api.medera.info`	`https://sandbox.api.medera.info`	Internally:

Backend: http://localhost (dev) / http://backend (Docker)
AI Services: http://localhost (dev) / http://ai-services (Docker)

Authentication

Surface	Credential	Header
End-user requests	session JWT	`Authorization: Bearer <jwt>`
Server-to-server	Developer API Key	`X-API-Key: <key>`
Service-to-service	Internal service key	`X-Service-Key: <key>` (internal only)	See Authentication Overview.

Content type

Request and response bodies are JSON. File uploads use multipart/form-data. Recordings, audio, and video uploads use multer (Backend) or UploadFile (AI Services). Max 150 MB per file.

Conventions

Convention	Detail
Pagination	Cursor-based — `?cursor=...&limit=50`
Idempotency	Optional `Idempotency-Key` header on POST / PATCH
Versioning	URL path — `/api/v1/...` implicit, `/api/v2/...` explicit
Rate limits	Per-endpoint, see Rate Limits
Errors	JSON `{ error: { code, message, request_id } }`

What’s next

Errors

Error format and common codes.

Rate Limits

Per-tenant limits.

Pagination

Cursor-based pagination.

Backend

AI Services

​Base URLs

​Authentication

​Content type

​Conventions

​What’s next