Developers

Build on unifeed

unifeed is a hosted social API. Your backend talks to unifeed; unifeed talks to Meta and X. No long-lived platform tokens in your database.

Base URL

All API routes live under /v1. Production base URL: https://unifeed.social. Local dev default: http://localhost:4000.

GET /health          → liveness check (no auth)

Quickstart

After creating an API key in the dashboard, list connected accounts for a tenant:

List accounts

curl "https://unifeed.social/api/v1/social-accounts?tenantId=YOUR_TENANT" \
  -H "Authorization: Bearer unifeed_YOUR_KEY"

Then publish to selected account IDs:

Create post

curl -X POST https://unifeed.social/api/v1/posts \
  -H "Authorization: Bearer unifeed_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "tenant_id": "YOUR_TENANT",
    "accounts": ["connected_account_id"],
    "containers": [{
      "content": "Shipped with unifeed",
      "media": [{ "url": "https://cdn.example.com/photo.jpg" }]
    }]
  }'

Integration flow

1. Authenticate

Every request to /api/v1 requires Authorization: Bearer <api_key>. Scope multi-tenant apps with tenant_id in the body or X-Tenant-Id header.

2. Configure platform apps

Add your Meta and X app credentials in the dashboard or via PUT /api/v1/platform-apps/:network so OAuth uses your own apps.

3. Connect accounts

POST /api/v1/social-networks/:network/auth-url, redirect the user, then finalize with selected page IDs.

4. Subscribe to events

Full API reference

Endpoint schemas, webhook payloads, and error codes.

Open documentation