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

# Get a post

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

Reference: https://api.docs.siftsy.com/api-reference/siftsy-analyst-api/get-post

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

- `postId` (string, required)

## Response

### 200

Post

- `data` (Post, optional) — One post as the dashboard sees it. Every field is always present; values Siftsy has not materialized are `null` (or `[]`).
- `meta` (EnvelopePostMeta, optional)

## Errors

### 403 Forbidden Error

Missing required scope

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

### EnvelopePostMeta

### 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": "p_301",
    "teamId": "team_2f8c1a",
    "status": "complete",
    "platform": "tiktok",
    "link": "https://www.tiktok.com/@acme/video/7311",
    "creator": {
      "username": "acme",
      "name": "Acme Running",
      "avatar": null
    },
    "title": "The new line is here",
    "summary": "Launch video for the new running line; creator demos the shoe and announces same-day shipping.",
    "description": "Same-day shipping on every order this week. #launch",
    "thumbnail": "https://cdn.example.com/p_301.jpg",
    "postType": "video",
    "tags": [
      "launch"
    ],
    "collectionIds": [
      "col_launch"
    ],
    "engagement": {
      "views": 812000,
      "likes": 40400,
      "comments": 4820,
      "shares": 1210,
      "saves": 3300,
      "engagementRate": 0.0605
    },
    "totalComments": 4820,
    "scores": {
      "scoreVersion": 3,
      "siftsyScore": 7.1,
      "sentiment": 6.8,
      "relevance": 7.9,
      "consensus": 7.2,
      "content": 6.9,
      "topic": 7
    },
    "sentimentMix": {
      "positivePercent": 44,
      "leanPositivePercent": 21,
      "neutralPercent": 14,
      "leanNegativePercent": 12,
      "negativePercent": 9
    },
    "postedAt": "2026-09-02T17:00:00.000Z",
    "addedByEmail": "teammate@acme.com",
    "addedVia": "dashboard",
    "automation": null,
    "dataVersion": 2,
    "createdAt": "2026-09-02T18:10:00.000Z",
    "updatedAt": "2026-09-03T04:12:44.000Z",
    "lastRefreshedAt": "2026-09-03T04:00:00.000Z",
    "lastProcessedAt": "2026-09-03T04:12:44.000Z",
    "isDemo": false,
    "vibe": null
  },
  "meta": {}
}
```

**SDK Code**

```python
import requests

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

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

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

print(response.json())
```

```javascript
const url = 'https://api.siftsy.app/analyst/v1/posts/postId';
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/posts/postId"

	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/posts/postId")

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/posts/postId")
  .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/posts/postId', [
  'headers' => [
    'Authorization' => 'Bearer <token>',
  ],
]);

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

```csharp
using RestSharp;

var client = new RestClient("https://api.siftsy.app/analyst/v1/posts/postId");
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/posts/postId")! 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()
```