Application API
Clear API and contract surface for Topolo Messaging, grouped under the application instead of split across generic reference sections.
Service IDs:
srv_topolo_messaging Repos: PlatformApplications/TopoloMessaging
Hosts:
https://messages.topolo.app Dependencies: topolo-auth, topolo-bugfix
Depends on Topolo Auth: yes
Type: curated
Source: PlatformApplications/TopoloMessaging/functions/api/messaging/[[path]].ts
Source exists: yes
Topolo Messaging is a Worker-with-assets application using shared Topolo UI Kit shell, launcher, Auth, command-palette, loading, and BugFix surfaces. It owns a Messaging D1 schema for workspaces, WhatsApp numbers, inboxes, contacts, conversations, messages, campaign drafts, automation definitions, outbound jobs, and webhook events. The app exposes /api/messaging/* for signed workspace operations, /api/auth/* as the same-origin Auth gateway, and /api/messaging/whatsapp/webhook for Meta webhook verification and signed event ingestion. Provider dispatch is queued through Cloudflare Queues; live WhatsApp Cloud API credentials must be provisioned as Worker secrets before outbound jobs move from provider_unconfigured to provider-sent states.
API key scopes in Auth catalog: 5
No global OpenAPI security scheme is declared.
automations.manage campaigns.manage inbox.read messages.send numbers.read Wrangler surfaces: PlatformApplications/TopoloMessaging/wrangler.toml
Environment variables: AUTH_API_URL
Routes: workers.dev or Pages-only delivery
Observability enabled: yes
First-party WhatsApp Business messaging, inbox, campaign, and automation application for Topolo.
Source: PlatformApplications/TopoloMessaging/package.json
Scripts: dev, build, build:worker, build:dispatch-worker, preview, check, db:migrate, db:migrate:remote, clean
Wrangler surfaces: PlatformApplications/TopoloMessaging/wrangler.toml
This application does not yet have a source-controlled OpenAPI spec in the docs platform. The current API page is derived from the registered contract source and repository surface.