Documentation built around the same resource model as the product.

Core features

• Unified social API: One API surface for projects, connected accounts, media, posts, scheduling, retries, and webhook delivery.
• Connected account lifecycle: Start OAuth, finalize pending connections, inspect account state, and disconnect cleanly by project.
• Media and preview pipeline: Reserve uploads, confirm media, attach assets to posts, and keep publish state connected to the right visuals.
• Operator visibility: Generation runs, retries, webhook history, quota pressure, and per-account publish outcomes stay visible in one console.

Resource groups

SignalForge groups resources the same way the operator console does: organizations, projects, accounts, media, content items, social posts, webhooks, usage, and delivery history.

• Social Networks: Connect a network, Get connected account details, Update connection settings, Disconnect a network, Get authentication URL
• Posts: Create a post, List posts, Get post details, Schedule or cancel publish, Inspect delivery lifecycle
• Media: Get upload URL, Confirm upload, List media files, Attach media to a post, Delete media
• Usage and workspace: Read plan limits, Track current usage, Manage invites, Update onboarding state, Review billing readiness

Start here

New workspaces should read the getting-started path first, then authentication, then webhooks. Platform constraints matter after the core project and account model is already clear.