Socialize

Documentation Map

• Application hub
• Application API surface
• Generated OpenAPI detail
• Machine system JSON
• Machine application JSON
• applications/socialize

What It Is

Social publishing and campaign tooling with brand-scoped API key bindings.

Canonical documentation for Socialize lives in `PlatformApplications/TopoloDocs`.

Use this repository for implementation only. Architecture, operational workflows, auth, billing behavior, and integration boundaries are canonical in the docs application rather than in repo-local markdown.

API Reference

Coverage: OpenAPI-backed

Source: PlatformApplications/TopoloSocialize/packages/worker/openapi.yaml

Source exists in repo: yes

The worker remains the primary API owner, and the authenticated web workspace renders through `TopoloAppShell`, inheriting shared Improve Topolo and TopoloNotify chrome while keeping brand workflows Socialize-owned. The browser app-switcher lane now reads Auth-owned catalog data through same-origin /api/auth/* on the Socialize host. `POST /api/brands/:brandId/transfer-organization` moves an existing brand to another accessible Topolo Auth organization by updating `brands.topolo_org_id` without changing the brand ID or content records. `PUT /api/posts/:id` supports reverting scheduled posts to drafts by clearing the schedule and returning draft state before the browser reports success, and now preserves explicit Facebook Page or Group, LinkedIn organization, and Instagram account target metadata during browser edits. `GET /api/integrations` now returns eligible Facebook Groups alongside Pages from the stored connection metadata and reports whether each provider is production-ready, sandbox-only, setup-required, or still planned. `POST /api/integrations/{platform}/connect` now rejects non-connectable providers up front instead of generating placeholder OAuth redirects. Nexus now supplies the org-wide image-generation default and allowed image-model catalog for Socialize image tools, and inline model overrides remain request-scoped and permission-gated instead of mutating the stored org setting. The worker now also exposes authenticated `GET /api/widget` for TopoloOne live workspace. Embedded password-login success completes through Socialize app navigation after shared Auth token persistence, login controls stay interactive while background auth bootstrap runs, and same-tab session-storage access-token restore preserves normal browser refreshes before cookie refresh completes. Socialize mobile resolves `topolo_auth_flutter` from the canonical Auth repo git package path and does not preload Auth identity from SharedPreferences.

App API page: /reference/apps/socialize

Generated OpenAPI page: /reference/generated/socialize

Operations: 31

Security schemes: BearerAuth (http), ApiKeyAuth (apiKey)

Auth and Permissions

Depends on Topolo Auth: yes

Service IDs:

API key scopes

Service permissions

accounts:read, accounts:write, analytics:read, api_keys:write, calendar:read, calendar:write, dashboard:read, posts:read, posts:write

Data Ownership

Deployments

Deployment environments: dev, stage, prod

Routes: workers.dev or Pages-only delivery

Observability enabled: yes

Wrangler surfaces

• PlatformApplications/TopoloSocialize/apps/web/wrangler.toml -> socialize
• PlatformApplications/TopoloSocialize/packages/scheduler/wrangler.toml -> socialize-scheduler
• PlatformApplications/TopoloSocialize/wrangler.toml -> socialize-prod-api

Build and deploy commands

• build — PlatformApplications/TopoloSocialize/apps/web/package.json :: tsc -b && vite build
• deploy:pages:prod — PlatformApplications/TopoloSocialize/apps/web/package.json :: pnpm build && pnpm exec wrangler pages deploy dist --project-name socialize --branch main
• preview — PlatformApplications/TopoloSocialize/apps/web/package.json :: vite preview
• build — PlatformApplications/TopoloSocialize/package.json :: pnpm -r run build
• build:worker — PlatformApplications/TopoloSocialize/package.json :: pnpm --filter=@socialize/worker... build
• build:scheduler — PlatformApplications/TopoloSocialize/package.json :: pnpm --filter=@socialize/scheduler build
• deploy:dev — PlatformApplications/TopoloSocialize/package.json :: pnpm build:worker && wrangler deploy --env dev
• deploy:stage — PlatformApplications/TopoloSocialize/package.json :: pnpm build:worker && wrangler deploy --env stage
• deploy:staging — PlatformApplications/TopoloSocialize/package.json :: pnpm run deploy:stage
• build — PlatformApplications/TopoloSocialize/packages/app/package.json :: tsc
• build — PlatformApplications/TopoloSocialize/packages/billing-webhook/package.json :: esbuild src/index.ts --bundle --outfile=dist/index.js --format=esm --platform=neutral --target=es2022 --external:@cloudflare/workers-types --main-fields=main --resolve-extensions=.ts,.js
• build:watch — PlatformApplications/TopoloSocialize/packages/billing-webhook/package.json :: pnpm build --watch
• build — PlatformApplications/TopoloSocialize/packages/cli/package.json :: shx rm -rf dist && tsc -b

Failure Modes

No default failure-mode heuristics are currently flagged for this system.

Debugging Runbooks

Start with these entrypoints:

• PlatformApplications/TopoloSocialize/apps/web/wrangler.toml
• PlatformApplications/TopoloSocialize/packages/scheduler/wrangler.toml
• PlatformApplications/TopoloSocialize/wrangler.toml
• PlatformApplications/TopoloSocialize/packages/worker/openapi.yaml
• PlatformApplications/TopoloSocialize/README.md
• PlatformApplications/TopoloSocialize/apps/web/package.json
• PlatformApplications/TopoloSocialize/package.json
• PlatformApplications/TopoloSocialize/packages/app/package.json
• PlatformApplications/TopoloSocialize/packages/billing-webhook/package.json
• PlatformApplications/TopoloSocialize/packages/cli/package.json

Change Log / Verification

Lifecycle: active

Last verified: 2026-04-27

Any code change to this system is expected to update the canonical docs in PlatformApplications/TopoloDocs and refresh the verification date.