Application API

Chat

Clear API and contract surface for Chat, grouped under the application instead of split across generic reference sections.

curated srv_topolo_chat_web

Documentation Map

Authority

Service IDs:

srv_topolo_chat_web

Repos: PlatformApplications/TopoloChat

Hosts:

https://chat.topolo.app https://topolo-chat.topolo.workers.dev

Dependencies: topolo-auth, applications-packages

Depends on Topolo Auth: yes

Contract Source

Type: curated

Source: PlatformApplications/TopoloDocs/src/content/public/applications/chat.mdx

Source exists: yes

Canonical Chat coverage now lives in the docs application. Chat mobile resolves `topolo_auth_flutter` from the canonical Auth repo git package path. The Chat web shell serves first-party /login through the branded shared LoginPage resolved from the `srv_topolo_chat_web` UI Kit registry entry, delegates third-party/provider handoff, returning-user cookie hydration, embedded password-login token persistence, and fallback callback restoration to the shared Topolo auth client, while Chat-owned app state completes successful password login by navigating to /app and the HTML document pre-consumes fresh one-time sso_code callbacks before React bootstraps. The authenticated workspace renders through `TopoloAppShell`, inheriting the shared Improve Topolo and TopoloNotify chrome while keeping Chat's channel, DM, and meeting rail product-owned. The Worker owns the same-origin /api/auth/* Auth data gateway, schedules organization-directory reconciliation after bootstrap, binds CHAT_UPLOADS to production and preview R2 upload buckets, exposes `GET /api/widget` with the shared `@topolo/sdk` widget response contract for TopoloOne live workspace, and accepts Calendar's token-authenticated `POST /api/internal/calendar/meetings` bridge to create Chat meetings plus guest invite URLs for `chat_meeting` bookings.

API key scopes in Auth catalog: 17

Auth Requirements

No global OpenAPI security scheme is declared.

  • api_keys.write
  • audit.read
  • channels.read
  • channels.write
  • direct_messages.read
  • direct_messages.write
  • meetings.read
  • meetings.write
  • messages.read
  • messages.write
  • operational_threads.read
  • operational_threads.write
  • search.read
  • settings.write
  • uploads.write
  • workspace.read
  • workspace.write

Runtime and Deployment

Wrangler surfaces: none detected

Environment variables: none derived

Routes: workers.dev or Pages-only delivery

Observability enabled: no explicit signal found

README-Derived Interface Surface

Source: PlatformApplications/TopoloChat/README.md

No route-level highlights were extracted from the current README.

Package Surfaces

topolo-chat

No package description recorded.

Source: PlatformApplications/TopoloChat/package.json

Scripts: build, deploy, dev, dev:web, desktop:build, desktop:dev, start, test, test:auth-contract, cf-typegen

Runtime Surface

Wrangler surfaces: No wrangler file detected in scanned surface

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.

Failure modes

  • No wrangler.toml surface was discovered under the registered repo paths.