Getting started

The shortest path from signup to a first published social post.

Create a workspace, generate a project API key, connect a social account, then send content into the publish pipeline. The dashboard is there for operators once the workflow becomes active.

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.

Creating an account

Go to the public SignalForge site and create an account with an organization name. That organization becomes the parent workspace for projects, invitations, quota tracking, and billing state.

After signup, the public site can bootstrap the first project and prepare the workspace for provider setup, media handling, and delivery controls.

Get an API key

Project API keys are created per project, not per organization. That keeps content ingestion, scheduled publish flows, and webhook-triggered automation scoped correctly.

POST /v1/projects/:projectId/api-keys
Authorization: Bearer USER_SESSION

{
  "label": "Production ingest key"
}

Using the API

Once a project has an API key and at least one connected provider account, content can be sent into the same intake model used across the product.

POST /v1/content-items
Authorization: Bearer PROJECT_API_KEY

{
  "title": "New story headline",
  "canonicalUrl": "https://example.com/story",
  "summary": "Context for the social pipeline",
  "platforms": ["x", "facebook"]
}