HTTP API Reference

This page summarizes the main HTTP route families in the AIOHM Platform.

Route Families

• routes/web.php contains central routes such as authentication helpers, documentation serving, and shared asset delivery
• routes/tenant.php contains tenant-domain routes such as login, registration, and tenant-facing UI entry points
• routes/api.php and related API files contain programmatic endpoints
• routes/ai.php contains MCP and AI tooling routes

Central Routes

These routes are not tied to a single tenant database.

Purpose	Example paths
Google auth	/auth/google/login, /auth/google/login/callback
Global docs	/docs/{path}
Shared assets	/tenancy/assets/{path}
Central registration handoff	/register

Tenant Routes

These routes activate on tenant domains and control tenant entry points.

Purpose	Example paths
User login	/login
User registration	/register
Demo login and onboarding	/demo-login
Tenant-specific application pages	registered through Filament and tenant route files

API Routes

The application exposes both operational endpoints and integration-oriented APIs.

Area	Example paths
Templates	api/templates/upload
WordPress tools	api/wp/content/generate, api/wp/post-types
Webhooks	api/webhooks/mautic, api/webhooks/postiz
Conversation uploads	api/v1/conversations/upload where enabled

Documentation Route Behavior

The /docs route now resolves:

• direct asset files
• clean URLs such as /docs/changelog
• directory-style URLs such as /docs/features/
• VitePress fallback routing when the requested page should be handled by the built client app

Working Rule

When documenting or extending APIs, treat the route files as the source of truth and use these reference pages as the public overview layer.