internal active Last verified 2026-03-29

Socialize Handbook

Internal handbook for the social publishing runtime, brand resource bindings, and OpenAPI-backed API surface.

Owners
marketing-platform
Source Repos
Applications/TopoloSocialize
Systems
Socialize, Topolo Auth
Tags
socialize, brands, publishing

What It Is

Socialize is the social publishing system for posts, media, campaigns, analytics, integrations, and brand-scoped publishing workflows.

Architecture

The system combines an application surface with a worker/API runtime that owns publishing operations while Auth owns the centralized bindable-resource catalog.

Runtime Surfaces

Socialize runtime hosts and worker routes are documented in the generated handbook and API pages.

API Reference

Use /reference/apps/socialize and the generated OpenAPI page for routes, operations, auth requirements, and copyable request examples.

Auth and Permissions

Socialize uses Auth-managed service IDs, API key scopes, and centralized brand resource-binding catalogs.

Data Ownership

Socialize owns the actual brand and content entities. Auth owns the machine-readable bindable-resource index used by TopoloOne.

Deployments

Socialize deploys with an application frontend and worker/API runtime surface.

Failure Modes

  • missing brands.read or related scopes
  • wrong API origin or CORS configuration
  • stale or empty Auth resource catalog for brand bindings

Debugging

  • verify the worker/API origin first
  • confirm the Auth service ID and scope catalog rows
  • inspect the resource sync path when brand bindings are missing

Change Log / Verification

  • Verified against the centralized brand resource-binding flow on 2026-03-29