> 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's aggregate score metrics

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

Requires `posts:read`. Returns the materialized per-post aggregate the
dashboard analysis view shows: overall scores plus five-bucket
percentage breakdowns for sentiment, relevance, and consensus.
Never recomputes. 404 `metrics_not_available` if the post has not
completed scoring. Score version 2+ also includes `content` and
`topic` mix bars (same five keys as sentiment).


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

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

- `data` (PostMetrics, optional)
- `meta` (EnvelopePostMetricsMeta, optional)

## Errors

### 404 Not Found Error

Resource not found

- `any`

## Types

### PostMetrics

- `postId` (string, optional)
- `scores` (PostScores, optional) — Scores resolved for the team's selected score version (1-10 scale). `content` / `topic` are populated for score version 2+ teams.
- `sentiment` (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.
- `relevance` (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.
- `consensus` (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.
- `content` (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.
- `topic` (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.
- `totalComments` (double, optional, nullable)
- `computedAt` (string, optional, nullable)

### EnvelopePostMetricsMeta

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

## Examples

**Response**

```json
{
  "data": {
    "postId": "string",
    "scores": {
      "scoreVersion": 1.1,
      "siftsyScore": 1.1,
      "sentiment": 1.1,
      "relevance": 1.1,
      "consensus": 1.1,
      "content": 1.1,
      "topic": 1.1
    },
    "sentiment": {
      "positivePercent": 1.1,
      "leanPositivePercent": 1.1,
      "neutralPercent": 1.1,
      "leanNegativePercent": 1.1,
      "negativePercent": 1.1
    },
    "relevance": {
      "positivePercent": 1.1,
      "leanPositivePercent": 1.1,
      "neutralPercent": 1.1,
      "leanNegativePercent": 1.1,
      "negativePercent": 1.1
    },
    "consensus": {
      "positivePercent": 1.1,
      "leanPositivePercent": 1.1,
      "neutralPercent": 1.1,
      "leanNegativePercent": 1.1,
      "negativePercent": 1.1
    },
    "content": {
      "positivePercent": 1.1,
      "leanPositivePercent": 1.1,
      "neutralPercent": 1.1,
      "leanNegativePercent": 1.1,
      "negativePercent": 1.1
    },
    "topic": {
      "positivePercent": 1.1,
      "leanPositivePercent": 1.1,
      "neutralPercent": 1.1,
      "leanNegativePercent": 1.1,
      "negativePercent": 1.1
    },
    "totalComments": 1.1,
    "computedAt": "string"
  },
  "meta": {}
}
```

**SDK Code**

```python
import requests

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

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

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

print(response.json())
```

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

	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/metrics")

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

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

```csharp
using RestSharp;

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