> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://api.docs.siftsy.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://api.docs.siftsy.com/_mcp/server.

## 1.5.0

**Refresh posts by API.** `POST /content/posts/refresh` (`posts:write`) re-fetches the comments of up to 100 posts already on the team — the same as **Resync** in the app — by `postIds` and/or `links`. It returns a `ContentJob` with `kind: refresh`; poll it like any content job. See [Adding content → Refresh posts](/guides/core-concepts/adding-content#refresh-posts-already-on-the-team).

Two rules, both visible on the job:

* **12-hour floor.** A given post on a given team is refreshed at most once every 12 hours through the API and through Siftsy Automations. Posts refreshed more recently are `skipped` with `reason: min_interval` and a `nextRefreshAt`, and are never charged. `minRefreshIntervalHours: 12` is on every refresh job.
* **Same credits as the app.** A refresh is free (`creditSource: included`, `creditCost: 0`) when the plan's included refresh cadence allows it; otherwise it spends one MAP or Ad Hoc credit (`creditSource: credit`), five with `capture.fullRead`. There is no separate refresh credit. `credits.included` counts the free ones; `credits.reserved` / `settled` / `refunded` sum the charged ones.

Also:

* New rate class `content_refresh` (10 / minute, 200 / day per key), listed under `rateLimit.routeClasses` on `GET /me`.
* `ContentJobLinkResult` gains `creditSource`, `creditCost`, `dataVersion`, and `nextRefreshAt` (refresh jobs only). New `reason` values: `min_interval`, `cooldown`, `not_found`, `not_on_team`, `unreachable`.
* Identical refresh requests are not replayed (unlike `POST /content/posts/add`); the floor already makes a repeat call free.
* **Siftsy Automations** (in the app) now follow the same 12-hour floor: Live Monitor's minimum cadence is `12h` (previously `1h`, default `2h`), and Lifecycle Refresh will not refresh a post within 12 hours of its last processing. Existing monitors with a shorter cadence keep running but fire at most every 12 hours.

## 1.4.4

**Base URL is now `/analyst/v1`.** Every Analyst API path lives under `https://api.siftsy.app/analyst/v1`.

* New base URL: `https://api.siftsy.app/analyst/v1` (local: `http://localhost:3000/analyst/v1`).
* `Location` headers use `/analyst/v1/...` — for example `/analyst/v1/analyses/an_…` and `/analyst/v1/content/jobs/cj_…`.
* `comments.path` is still relative to the base URL. Do not prepend `/analyst/v1` a second time.
* The previous prefix `/v1/client` still works as a deprecated alias. Point new integrations at `/analyst/v1`.

## 1.4.3

**Renamed: Siftsy Data API → Siftsy Analyst API.** Documentation only — nothing about the API itself changed.

The Analyst API helps analysts use Siftsy effectively in their workflows: **import flagged content** into a team (posts by URL, or a public account's recent posts, through the [content routes](/guides/core-concepts/adding-content)) and **export key analyses and insights** — posts, collections, scores, analyses, and saved reports — into data warehouses, data platforms, and BI tools ([BI sync](/guides/core-concepts/bi-sync)).

* Base URL (`/v1/client`), endpoints, scopes, key prefixes (`sk_live_` / `sk_test_`), headers, rate limits, and response shapes are unchanged. Existing keys and integrations keep working with no action.
* The [Overview](/guides/get-started/overview) is rewritten around the import → analyze → export workflow.