> 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.

# List posts in a collection

GET https://api.siftsy.app/analyst/v1/collections/{collectionId}/posts

Requires `collections:read` and `posts:read`. Campaign ids include
posts from all nested subgroups. Defaults to completed posts
(including posts mid-resync that still have prior data).

Supports the same post filters as `GET /posts` (link, account,
platform, posted date range, Siftsy score, sentiment percentages).
All filters combine with AND.

Each request walks the team's posts for a bounded time. When a
collection is sparse, a page can come back with fewer than `limit`
posts (even zero), `hasMore: true`, a `nextCursor`, and
`meta.partialPage: true`. Keep following `nextCursor` until
`hasMore` is false.

Rate class `collection_posts` (60 / minute, 1,000 / day per key).


Reference: https://api.docs.siftsy.com/api-reference/siftsy-analyst-api/list-collection-posts

## Authentication

- `Authorization` header (bearer token, required) — Bearer authentication of the form `Bearer <token>`, where token is your auth token.
- `X-Api-Key` header (required) — API Key authentication via header

## Servers

- `https://api.siftsy.app/analyst/v1` (Production, default)
- `http://localhost:3000/analyst/v1` (Local development)

## Request

### Path parameters

- `collectionId` (string, required)

### Query parameters

- `cursor` (string, optional)
- `limit` (integer, optional, default: 25)
- `status` (enum, optional, default: complete)
  - Allowed values: `complete`, `pending`, `archived`, `unreachable`, `cancelled`, `holding`, `all`
- `link` (string, optional) — Only posts with this URL. Scheme, `www.`, query string, hash, trailing slash and case are ignored, so tracking parameters never break a match. Comma-separate or repeat the parameter to match several links.
- `account` (string, optional) — Only posts from this creator. Matches the creator username or display name, case-insensitive; a leading `@` is optional. Comma-separate or repeat the parameter to match several accounts.
- `tag` (string, optional) — Only posts carrying this content tag (case-insensitive, leading `#` optional). Comma-separate or repeat the parameter to match any of several tags.
- `platform` (string, optional) — Only posts from these platforms (case-insensitive, e.g. `instagram`, `tiktok`, `youtube`). Comma-separate to match several.
- `posted_since` (datetime, optional) — Only posts published on or after this date (ISO 8601).
- `posted_until` (datetime, optional) — Only posts published on or before this date (ISO 8601).
- `updated_since` (datetime, optional) — Only posts whose Siftsy data changed on or after this date (ISO 8601). Useful for incremental syncs.
- `min_score` (double, optional) — Only posts with a Siftsy score at or above this value (0–10). Posts that have not been scored yet are excluded.
- `max_score` (double, optional) — Only posts with a Siftsy score at or below this value (0–10).
- `min_positive_percent` (double, optional) — Only posts where `sentimentMix.positivePercent` is at or above this value (0–100).
- `max_positive_percent` (double, optional) — Only posts where `sentimentMix.positivePercent` is at or below this value (0–100).
- `min_lean_positive_percent` (double, optional) — Only posts where `sentimentMix.leanPositivePercent` is at or above this value (0–100).
- `max_lean_positive_percent` (double, optional) — Only posts where `sentimentMix.leanPositivePercent` is at or below this value (0–100).
- `min_neutral_percent` (double, optional) — Only posts where `sentimentMix.neutralPercent` is at or above this value (0–100).
- `max_neutral_percent` (double, optional) — Only posts where `sentimentMix.neutralPercent` is at or below this value (0–100).
- `min_lean_negative_percent` (double, optional) — Only posts where `sentimentMix.leanNegativePercent` is at or above this value (0–100).
- `max_lean_negative_percent` (double, optional) — Only posts where `sentimentMix.leanNegativePercent` is at or below this value (0–100).
- `min_negative_percent` (double, optional) — Only posts where `sentimentMix.negativePercent` is at or above this value (0–100).
- `max_negative_percent` (double, optional) — Only posts where `sentimentMix.negativePercent` is at or below this value (0–100).

## Response

### 200

Post page (newest first)

- `data` (list of Post, optional)
- `meta` (EnvelopePostsMeta, optional)

## Errors

### 400 Bad Request Error

Invalid request

- `any`

### 404 Not Found Error

Resource not found

- `any`

## Types

### Post

One post as the dashboard sees it. Every field is always present; values Siftsy has not materialized are `null` (or `[]`).

- `id` (string, optional)
- `teamId` (string, optional, nullable)
- `status` (string, optional, nullable) — Processing state (`complete`, `pending`, `archived`, `unreachable`, `cancelled`, `holding`, …)
- `platform` (string, optional, nullable)
- `link` (string, optional, nullable)
- `creator` (Creator, optional) — The account that published the post.
- `title` (string, optional, nullable)
- `summary` (string, optional, nullable) — Siftsy's short content brief for the post
- `description` (string, optional, nullable) — Caption / description as published
- `thumbnail` (string, optional, nullable)
- `postType` (string, optional, nullable)
- `tags` (list of string, optional) — Content tags teammates put on the post (filter with `tag=`)
- `collectionIds` (list of string, optional) — Collections (campaigns / groups) the post belongs to
- `engagement` (Engagement, optional) — Platform engagement counts as last refreshed. Null when the platform does not report a metric.
- `totalComments` (double, optional, nullable) — Comments Siftsy captured and scored
- `scores` (PostScores, optional) — Scores resolved for the team's selected score version (1-10 scale). `content` / `topic` are populated for score version 2+ teams.
- `sentimentMix` (ScoreBuckets, optional) — Five-bucket percentage breakdown. Dashboard labels per dimension — Sentiment: Positive / Lean positive / Neutral / Lean negative / Negative. Content: Supportive (positive) / Receptive (leanPositive) / Split (neutral) / Skeptical (leanNegative) / Opposed (negative). Topic: Enthusiastic (positive) / Favorable (leanPositive) / Mixed (neutral) / Critical (leanNegative) / Hostile (negative). Relevance: On-topic (positive) / Relevant (leanPositive) / General (leanNegative) / Off-topic (negative). Consensus: Agreeing (positive) / Discussing (leanPositive) / Debating (leanNegative) / Fighting (negative). neutralPercent is typically unused for relevance and consensus.
- `postedAt` (string, optional, nullable) — When the post was published (ISO 8601; filter with `posted_since` / `posted_until`)
- `addedByEmail` (string, optional, nullable) — Teammate who added the post to Siftsy
- `addedVia` (enum, optional) — `api` when the post was added through `POST /content/...`; `automation` when a Siftsy Automation (for example an account watch) pulled it in; `dashboard` otherwise
  - Allowed values: `dashboard`, `api`, `automation`
- `automation` (PostAutomation, optional, nullable) — Automation provenance. `null` when no Siftsy Automation has added or refreshed the post. `addedByEmail` on an automation-added post is the teammate who set up the automation; on a refreshed post it stays the original uploader.
- `dataVersion` (double, optional, nullable)
- `createdAt` (string, optional, nullable) — When the post was added to Siftsy
- `updatedAt` (string, optional, nullable) — When Siftsy last changed the post's data (the `updated_since` watermark)
- `lastRefreshedAt` (string, optional, nullable) — Last engagement / comment refresh from the platform
- `lastProcessedAt` (string, optional, nullable) — Last time scoring finished
- `isDemo` (boolean, optional) — Demo / staff-uploaded post; does not imply billing usage
- `vibe` (PostVibe, optional, nullable, deprecated) — Legacy aggregate kept for early integrations. Use `scores` and `sentimentMix` instead; this object may be removed in a future major version.

### EnvelopePostsMeta

### Creator

The account that published the post.

- `username` (string, optional, nullable)
- `name` (string, optional, nullable) — Display name
- `avatar` (string, optional, nullable) — Avatar URL

### Engagement

Platform engagement counts as last refreshed. Null when the platform does not report a metric.

- `views` (double, optional, nullable)
- `likes` (double, optional, nullable)
- `comments` (double, optional, nullable)
- `shares` (double, optional, nullable)
- `saves` (double, optional, nullable)
- `engagementRate` (double, optional, nullable)

### PostScores

Scores resolved for the team's selected score version (1-10 scale). `content` / `topic` are populated for score version 2+ teams.

- `scoreVersion` (double, optional)
- `siftsyScore` (double, optional, nullable)
- `sentiment` (double, optional, nullable)
- `relevance` (double, optional, nullable)
- `consensus` (double, optional, nullable)
- `content` (double, optional, nullable)
- `topic` (double, optional, nullable)

### ScoreBuckets

Five-bucket percentage breakdown. Dashboard labels per dimension — Sentiment: Positive / Lean positive / Neutral / Lean negative / Negative. Content: Supportive (positive) / Receptive (leanPositive) / Split (neutral) / Skeptical (leanNegative) / Opposed (negative). Topic: Enthusiastic (positive) / Favorable (leanPositive) / Mixed (neutral) / Critical (leanNegative) / Hostile (negative). Relevance: On-topic (positive) / Relevant (leanPositive) / General (leanNegative) / Off-topic (negative). Consensus: Agreeing (positive) / Discussing (leanPositive) / Debating (leanNegative) / Fighting (negative). neutralPercent is typically unused for relevance and consensus.

- `positivePercent` (double, optional, nullable)
- `leanPositivePercent` (double, optional, nullable)
- `neutralPercent` (double, optional, nullable)
- `leanNegativePercent` (double, optional, nullable)
- `negativePercent` (double, optional, nullable)

### PostAutomation

Automation provenance. `null` when no Siftsy Automation has added or refreshed the post. `addedByEmail` on an automation-added post is the teammate who set up the automation; on a refreshed post it stays the original uploader.

- `addedById` (string, optional, nullable) — Automation that pulled the post in (set only when `addedVia` is `automation`)
- `ids` (list of string, optional) — Every automation that has added or refreshed this post
- `lastRefreshAt` (string, optional, nullable) — Last time an automation (live monitor / lifecycle refresh) resynced the post
- `refreshCount` (double, optional) — How many automation-driven resyncs the post has had

### PostVibe

Legacy aggregate kept for early integrations. Use `scores` and `sentimentMix` instead; this object may be removed in a future major version.

- `score` (double, optional, nullable)
- `sentiment` (any, optional, nullable)
- `positivePercent` (double, optional, nullable)
- `neutralPercent` (double, optional, nullable)
- `negativePercent` (double, optional, nullable)

## Examples

**Response**

```json
{
  "data": [
    {
      "id": "string",
      "teamId": "string",
      "status": "string",
      "platform": "string",
      "link": "string",
      "creator": {
        "username": "string",
        "name": "string",
        "avatar": "string"
      },
      "title": "string",
      "summary": "string",
      "description": "string",
      "thumbnail": "string",
      "postType": "string",
      "tags": [
        "string"
      ],
      "collectionIds": [
        "string"
      ],
      "engagement": {
        "views": 1.1,
        "likes": 1.1,
        "comments": 1.1,
        "shares": 1.1,
        "saves": 1.1,
        "engagementRate": 1.1
      },
      "totalComments": 1.1,
      "scores": {
        "scoreVersion": 1.1,
        "siftsyScore": 1.1,
        "sentiment": 1.1,
        "relevance": 1.1,
        "consensus": 1.1,
        "content": 1.1,
        "topic": 1.1
      },
      "sentimentMix": {
        "positivePercent": 1.1,
        "leanPositivePercent": 1.1,
        "neutralPercent": 1.1,
        "leanNegativePercent": 1.1,
        "negativePercent": 1.1
      },
      "postedAt": "string",
      "addedByEmail": "string",
      "addedVia": "dashboard",
      "automation": {
        "addedById": "string",
        "ids": [
          "string"
        ],
        "lastRefreshAt": "string",
        "refreshCount": 1.1
      },
      "dataVersion": 1.1,
      "createdAt": "string",
      "updatedAt": "string",
      "lastRefreshedAt": "string",
      "lastProcessedAt": "string",
      "isDemo": true,
      "vibe": {
        "score": 1.1,
        "sentiment": null,
        "positivePercent": 1.1,
        "neutralPercent": 1.1,
        "negativePercent": 1.1
      }
    }
  ],
  "meta": {}
}
```

**SDK Code**

```python
import requests

url = "https://api.siftsy.app/analyst/v1/collections/collectionId/posts"

querystring = {"link":"https://www.instagram.com/reel/ABC123/","account":"@nike","tag":"launch","platform":"instagram,tiktok","posted_since":"2026-01-01","posted_until":"2026-03-31T23:59:59Z","min_score":"7","min_positive_percent":"60","max_negative_percent":"10"}

headers = {"Authorization": "Bearer <token>"}

response = requests.get(url, headers=headers, params=querystring)

print(response.json())
```

```javascript
const url = 'https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10';
const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}
```

```go
package main

import (
	"fmt"
	"net/http"
	"io"
)

func main() {

	url := "https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10"

	req, _ := http.NewRequest("GET", url, nil)

	req.Header.Add("Authorization", "Bearer <token>")

	res, _ := http.DefaultClient.Do(req)

	defer res.Body.Close()
	body, _ := io.ReadAll(res.Body)

	fmt.Println(res)
	fmt.Println(string(body))

}
```

```ruby
require 'uri'
require 'net/http'

url = URI("https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10")

http = Net::HTTP.new(url.host, url.port)
http.use_ssl = true

request = Net::HTTP::Get.new(url)
request["Authorization"] = 'Bearer <token>'

response = http.request(request)
puts response.read_body
```

```java
import com.mashape.unirest.http.HttpResponse;
import com.mashape.unirest.http.Unirest;

HttpResponse<String> response = Unirest.get("https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10")
  .header("Authorization", "Bearer <token>")
  .asString();
```

```php
<?php
require_once('vendor/autoload.php');

$client = new \GuzzleHttp\Client();

$response = $client->request('GET', 'https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10', [
  'headers' => [
    'Authorization' => 'Bearer <token>',
  ],
]);

echo $response->getBody();
```

```csharp
using RestSharp;

var client = new RestClient("https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10");
var request = new RestRequest(Method.GET);
request.AddHeader("Authorization", "Bearer <token>");
IRestResponse response = client.Execute(request);
```

```swift
import Foundation

let headers = ["Authorization": "Bearer <token>"]

let request = NSMutableURLRequest(url: NSURL(string: "https://api.siftsy.app/analyst/v1/collections/collectionId/posts?link=https%3A%2F%2Fwww.instagram.com%2Freel%2FABC123%2F&account=%40nike&tag=launch&platform=instagram%2Ctiktok&posted_since=2026-01-01&posted_until=2026-03-31T23%3A59%3A59Z&min_score=7&min_positive_percent=60&max_negative_percent=10")! as URL,
                                        cachePolicy: .useProtocolCachePolicy,
                                    timeoutInterval: 10.0)
request.httpMethod = "GET"
request.allHTTPHeaderFields = headers

let session = URLSession.shared
let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
  if (error != nil) {
    print(error as Any)
  } else {
    let httpResponse = response as? HTTPURLResponse
    print(httpResponse)
  }
})

dataTask.resume()
```