> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meridian.study/llms.txt
> Use this file to discover all available pages before exploring further.

# API reference

> Meridian HTTP APIs documented on this site

## Scope

This section documents **Meridian** HTTP APIs and related contracts as maintained for Study Compass engineering. Narrative pages under **`api-reference/`** (for example [Event management](/api-reference/event-management)) carry the detailed paths, payloads, and behavior aligned with the **Express** backend in `Meridian/backend/`.

## Authentication

The Meridian **web client** uses **cookie-backed JWT** access and refresh flows; frontend code should go through **`useFetch`** and **`postRequest`** ([Web client best practices](/frontend/best-practices)), not ad hoc clients. Individual API pages state whether a route expects a session cookie, a Bearer token, or a public call.

## OpenAPI file

The repository may include **`api-reference/openapi.json`** for Mintlify tooling or future playground generation. Until that file is fully curated for Meridian, treat the **MDX API pages** in this tab as authoritative.

## Related pages

<CardGroup cols={2}>
  <Card title="Event management API" icon="calendar" href="/api-reference/event-management">
    Organization events, agendas, RSVPs, and related HTTP operations.
  </Card>

  <Card title="Backend best practices" icon="server" href="/backend/best-practices">
    Route layout, `req.db`, `verifyToken`, and how Express handlers are structured.
  </Card>

  <Card title="Authentication overview" icon="shield" href="/backend/auth/overview">
    Cookie vs Bearer JWTs, refresh, and which routes require a logged-in user.
  </Card>

  <Card title="Web client best practices" icon="browser" href="/frontend/best-practices">
    `useFetch` and `postRequest`—the supported way to call these APIs from the web app.
  </Card>

  <Card title="Multi-tenant identity" icon="users" href="/backend/multi-tenant-identity">
    How `globalUserId` and memberships affect authorization on tenant subdomains.
  </Card>

  <Card title="Atlas event dashboard" icon="table-columns" href="/atlas/event-dashboard">
    Organizer-facing flows that sit on top of the event management API.
  </Card>
</CardGroup>