> Production API availability: use /api/v1/help?view=guides and the resource operations catalog before following a recipe. Some localhost capabilities are not deployed yet; an absent operation is unavailable.
Choose the owning module
This reference inventories 25 application modules and 71 explicitly registered versioned routes. It separates agent APIs from session and machine interfaces. Source inspection is not a live certification of every mutation.
- Analytics: First-party event collection and analysis. The public collector and the session-scoped reporting APIs have different trust boundaries.
- Calendar: Calendar and scheduling editor actions. Keep calendar records separate from a website section displaying them.
- Carousel: Reusable slide decks built from uploaded image assets, with draft and published states.
- Corporate: Internal corporate records and administration. Treat these as private operational data until a specific publication contract exists.
- Dashboard: Website records, deployment aliases and deployment status. Dashboard identifies the destination; Databoard supplies its generated application.
- Databoard: Page structure, HMVC contracts, section templates, source mappings and deployment configuration.
- Discussions: Discussion records and their browser workflows. These are separate from generated-site member comments.
- Docs: Collections and ordered chapters. Databoard consumes the selected public projection to generate documentation pages.
- Ecommerce: Store catalogs, product prices and the catalog projection used by generated-site checkout and access decisions.
- Forms: Form authoring, submission contracts, workflow configuration and publication to generated sites.
- Groups: Associations between users, records and websites. A group association is not a substitute for an ownership or authorization check.
- Labs: Training intent, evaluation plans, run manifests and metrics. The kernel/runtime repository owns execution; a plan is not an executed training run.
- Identity and shared API services: API-key identity, scopes, sign-in and central authentication. Generated-site member authentication is a separate account boundary.
- Mail Campaigns: Campaign drafts, lists, audiences, recipient rendering and preference handling. Preparing content is separate from sending mail.
- Masterclass: Ebook and curriculum authoring. Published content is projected into generated sites; Ecommerce controls associated selling configuration.
- Notes: Canonical articles, publication state, group associations and channel-specific syndication variants.
- Notification: Notification delivery and browser-facing notification management. Do not assume its editor actions form an agent API.
- Profile: Profile records and short profile posts. The agent interface below concerns posts, not unrestricted editing of account identity.
- Recruit: Recruitment editor workflows. Public recruitment content and private applicant records need separate access rules.
- Research Logging: Agent-proposed research work logs with validation, idempotency and a human review stage before accepted records.
- Resume: Structured resume profiles with guarded edits to experience and project entries.
- Sales: Sales workflows and their browser actions. Treat account and pipeline information as private operational data.
- Scheduler: Scheduled work and its editor handlers. A configured schedule does not establish that a worker is running.
- Settings: Application settings. Changing an internal setting may affect other modules; keep its ownership and side effects explicit.
- Workflows: The standalone Workflows module. It is not the same API as a Form’s workflow configuration and delivery queue.
Design and validation
Maintain this reference
Discover the machine-readable catalog through GET /api/v1/help?view=guides and resource operations through GET /api/v1/help?view=operations&resource=RESOURCE. The catalog is not a complete OpenAPI schema and does not certify runtime authorization.