> ## Documentation Index
> Fetch the complete documentation index at: https://docs.postsiva.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Sign up at postsiva.com, create a workspace, connect accounts, create an API key, and publish your first post.

Follow these steps in order — all setup happens in the [Postsiva app](https://postsiva.com) first, then you automate with the REST API or MCP.

## 1. Sign up or log in

Go to [postsiva.com](https://postsiva.com) and **sign up** (email + OTP + password) or **log in**.

## 2. Create a workspace

Create a **workspace** or accept an invite. Pick the workspace you will use for API access (switcher in the app header). OAuth tokens, posts, drafts, and your API key are all scoped to this workspace.

## 3. Connect your accounts

**Settings → Integrations** → connect each network you need (LinkedIn, Instagram, Facebook, TikTok, YouTube, Threads, Pinterest, Bluesky, …).

* Complete OAuth in the browser popup for each platform.
* **Facebook:** select the Pages you want to manage.
* **LinkedIn:** connect org pages if you post as a company.
* **Bluesky:** use handle + app password (no OAuth popup).

<Note>
  You need **Pro** for API keys. Upgrade under **Settings → Billing** if API Keys is locked.
</Note>

Alternatively, after you have an API key, connect via [OAuth API](/apis/oauth):

```bash theme={null}
curl -X POST "https://backend.postsiva.com/unified/oauth/url" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: psk_live_YOUR_KEY" \
  -d '{"platform":["linkedin","instagram"]}'
```

Open each returned `auth_url` to finish linking.

## 4. Create your API key

1. Open **Settings → API Keys**.
2. Click **Create API Key** — name it (e.g. `production`) and choose a [scope](/reference/ids-and-scopes#api-key-scopes) (`full` for most integrations).
3. Copy `psk_live_…` **once** — it is not shown again.

This key is how you call **all REST endpoints** (`/unified/post/*`, `/unified/posts`, `/unified/analytics`, …). Workspace is inferred from the key — no `X-Workspace-Id` required.

<Warning>
  Store your key securely. Revoke and recreate if exposed.
</Warning>

## 5. Send your first REST post

```bash theme={null}
curl -X POST "https://backend.postsiva.com/unified/post/text" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: psk_live_YOUR_KEY" \
  -d '{
    "platforms": ["linkedin", "threads"],
    "default_text": "Hello from the Postsiva API!"
  }'
```

<ResponseField name="results" type="array">
  Per-platform success/error objects with post metadata.
</ResponseField>

### Schedule for later

Add `scheduled_time` (ISO 8601 UTC):

```json theme={null}
{
  "platforms": ["linkedin"],
  "default_text": "Scheduled post",
  "scheduled_time": "2026-07-10T14:30:00Z"
}
```

### Save as draft

```json theme={null}
{
  "platforms": ["linkedin"],
  "default_text": "Draft caption",
  "draft": true
}
```

## 6. Or connect Unified MCP

Same API key for AI agents (Cursor, Claude, etc.):

```bash theme={null}
# URL: https://mcp.postsiva.com/mcp
# Header: X-API-Key: psk_live_YOUR_KEY
```

See [Connect to MCP](/mcp/connect).

## 7. Verify

* Check the platform, or
* `GET https://backend.postsiva.com/unified/posts?platforms=linkedin&limit=5` with your API key

## Next steps

<CardGroup cols={2}>
  <Card title="Complete setup" icon="route" href="/guides/complete-setup">
    Full UI + programmatic OAuth flow.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Headers, scopes, and plan requirements.
  </Card>

  <Card title="API Overview" icon="code" href="/apis/overview">
    All REST endpoint groups.
  </Card>

  <Card title="Posting guide" icon="paper-plane" href="/apis/posting">
    Text, image, video, carousel, drafts, scheduling.
  </Card>
</CardGroup>