Skip to main content
Was this helpful?

PrimeCal Developer Docs

Code-Backed API Reference By Product Area

This section mirrors the actual product feature map. It documents the non-admin backend directly from the NestJS controllers and DTOs, with request constraints, auth notes, example calls, and implementation caveats.

Non-admin scopeController-backedJWT, API key, and agent authMCP included

Start Here

Overview

API Overview

Base path, auth modes, scope rules, and the full product-area map.

Authentication

Authentication API

Registration, onboarding, login, MFA, OAuth, refresh flow, and user API keys.

Profile

User API

Profile settings, language, permission bootstrap, and sharing helpers.

Automation

Automation API

Rules, triggers, conditions, actions, audit logs, approvals, and webhooks.

AI Agents

Agent API

Agent CRUD, scoped permissions, issued keys, and the MCP runtime endpoints.

Product Areas

Planning

Calendar, Events, Tasks

Calendars, groups, sharing, event CRUD and recurrence, comments, task CRUD, and labels.

Integrations

External Sync

Provider status, OAuth handoff, external calendar mapping, disconnect, and manual sync.

Platform

Platform API

Health, readiness, feature flags, monitoring, frontend error ingestion, and security reports.

  1. Read API Overview.
  2. Pick the product area that matches the user-facing feature you are building.
  3. Use the endpoint tables and DTO rules before wiring client requests.
  4. Treat anything under admin controllers as a separate documentation surface.

Swagger UI

When enabled by the backend, generated Swagger UI is served at /api/docs. Production deployments can place HTTP Basic authentication in front of that route.