1.4.1
Documentation only — no API behavior changed.
- Adding content is a core concept, separate from the read pipeline. The Overview keeps Select → Analyze → Comments as the three-step read path and adds a distinct Adding content section for the write path (
POST /content/…→ job → posts process → readable), with its own guide card. In the sidebar it follows Retrieving comments, after the read-pipeline pages. - Adding content now walks through the ingest process end to end: the order of operations for
POST /content/posts/add(validate → target team → collections → replay → dedupe → fund check → reserve + create → queue) and forPOST /content/accounts/add(request-side steps, then discover → filter → add in a worker), plus a post-lifecycle table showing which statuses reserve, consume, or refund a credit and when a post becomes readable. The two POST operations in the API reference summarize the same order. - Authentication and the Quickstart now state the plan requirement (Powerhouse / Enterprise) and describe key management: create, rotate, revoke, scope toggles, and the usage view.
- Rate limits gains a Usage history section explaining what Team Settings → API shows and how it relates to the daily budgets.
Post.addedViais fully enumerated in the reference:dashboard,api, orautomation(posts pulled in by a Siftsy Automation on a schedule). Previouslyautomationwas returned but not listed. BI sync documents the field alongsideaddedByEmail.- The API reference description notes the plan requirement.