Authentication | Siftsy Analyst API

Create a Siftsy Analyst API key in the Siftsy dashboard under Team Settings → API (team admin). The full key is shown once, so copy it right away.

The base URL is https://api.siftsy.app/analyst/v1.

The Siftsy Analyst API is included on Powerhouse and Enterprise plans (including Enterprise sub-teams). On other plans the API tab is not available; contact Siftsy if you need API access on a custom plan.

Send either:

Authorization: Bearer sk_test_...

X-Api-Key: sk_test_...

Production keys use the sk_live_ prefix; non-prod uses sk_test_.

Scopes

Scope	Access
`posts:read`	List/get posts and per-post metrics
`comments:read`	Sample comments behind a post or selection analysis (evidence, not a full-thread export)
`insights:read`	Read analyses teammates saved or shared in the Siftsy app (`GET /snapshots`, `GET /insights`)
`analyses:read`	Read analyses and saved campaign reports (up to 1,000 posts)
`analyses:run`	Create analyses from a content selection (`POST /analyses`)
`collections:read`	List/get collections and posts by collection
`team:read`	Team metadata and analysis settings
`posts:write`	Opt-in. Add posts by URL (`POST /content/posts/add`). Spends the team’s MAPs / Ad Hoc credits
`accounts:write`	Opt-in. Add a public account’s recent posts (`POST /content/accounts/add`). Spends credits

The read scopes are granted to every new key. The two write scopes are off by default: a team admin turns them on for a specific key when creating or rotating it. A key without them cannot add content or spend credits. See Adding content.

Keys never grant billing access or Siftsy staff privileges. analyses:run only creates API-owned analysis resources that expire after 7 days; it cannot rescore posts or change collections. Write scopes add content the same way the app does — they cannot delete or rescore posts, and they can only create collections when you add posts to a new collection name.

Keys created before a scope existed do not have it. Rotate the key or create a new one to pick up new scopes.

Managing keys

Up to 3 active keys per team. In Team Settings → API a team admin can:

Create a key and choose its scopes. Read scopes are on; the write scopes are an explicit toggle.
Rotate a key — a new secret with the scopes you choose; the old secret stops working. This is how an existing key picks up scopes it did not have.
Revoke a key immediately.
See usage — requests and response bytes per key, per UTC day, for the last 30 days, alongside the limits in force. These are the same counters the rate limiter uses, so what you see there is what counts against your budget.