Application API
Clear API and contract surface for Social Studio, grouped under the application instead of split across generic reference sections.
App IDs:
app_topolo_social_studio Repos:
Hosts:
https://studio.topolo.app https://studio-api.stg.topolo.us https://studio.stg.topolo.us Dependencies: topolo-auth, applications-packages, topolo-nexus
Depends on Topolo Auth: yes
Type: curated
Source: PlatformApplications/TopoloSocialStudio/package.json
Source exists: no
Canonical public and internal docs now cover the hybrid desktop, worker, and Nexus-backed AI generation model. The marketing web and desktop shells delegate browser login handoff and one-time sso_code callback redemption to the shared Topolo auth client through the Social Studio application wrapper, with callback effects kept single-pass so one status update cannot cancel the active exchange/bootstrap. The authenticated web and desktop shells render through `TopoloAppShell`, inheriting the shared account, launcher, account-menu Improve Topolo, and TopoloNotify chrome while keeping Studio project navigation product-owned and avoiding standalone floating report controls. Nexus owns the org-wide image-generation default and allowed model catalog for Studio workspaces, while the generate step may expose per-run inline overrides only to callers with the required workspace authority. Social Studio owns the stable Auth service slug `topolo-social-studio`; workers and browser shells resolve the concrete app id from Topolo Auth at runtime through `/api/app-identity`.
API key scopes in Auth catalog: 11
No global OpenAPI security scheme is declared.
api_keys.write approvals.write assets.read assets.write briefs.read briefs.write exports.read generation.write settings.write workspace.read workspace.write Wrangler surfaces: none detected
Environment variables: none derived
Routes: workers.dev fallback or no explicit route declared
Observability enabled: no explicit signal found
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.