LinkedIn API: Profile — Post metrics by username

What this endpoint does

What you can build with this API method

Review the result and common workflows first, then move to parameters and a working request example.

What this endpoint helps with

The response provides a ready-to-use Profile summary with key counters and metrics in the selected API format.

When to use it

Use “Post metrics by username” for dashboards, scoring, and recurring reports that need a compact metric snapshot.

Common use cases

Product dashboards

Show core LinkedIn metrics without loading and processing an entire collection.

Trend monitoring

Store periodic snapshots and compare metric changes over time.

Object scoring

Use aggregate metrics as inputs for internal rankings and rules.

Available versions

Response version

Both versions solve the same job and accept the same parameters. Use the switch to compare the response structure and choose the version your client expects.

Response version V2

Switch versions on this page to compare response structures while keeping the same documentation URL.

V1 Not available

What stays the same

Authentication, required parameters, and the request shape stay the same across V1 and V2. In practice, you choose the version when you build the endpoint path and when you parse the response.

What changes between versions

The main difference is the response envelope. Use V2 for new integrations and keep V1 only when you need compatibility with an existing client contract.

How to use it

How to call the method

Use the same API key header and the same query parameters for both versions. This documentation shows the shared parameter set first, then version-specific endpoint paths and code snippets.

Input parameters

Shared parameters

Parameter	Required	Type	Example	Description
`username`	Yes	`str`	`value`	Public username without the @ symbol.

Version-specific request path

V2

Choose a version when you copy the exact endpoint path, example URL, and code snippet. The parameter list above stays the same.

GET /api/v2/linkedin.com/profile/posts-metrics-by-username

Normalized format

Request preview

Base URL https://www.scrapestorm.net

Endpoint /api/v2/linkedin.com/profile/posts-metrics-by-username

Required parameters

username

Optional parameters

None

Example URL

https://www.scrapestorm.net/api/v2/linkedin.com/profile/posts-metrics-by-username?username=value

Code examples

curl --request GET \
  --url "https://www.scrapestorm.net/api/v2/linkedin.com/profile/posts-metrics-by-username" \
  --header "X-API-Key: 00000000-0000-4000-8000-000000000000" \
  --get --data-urlencode 'username=value'

from urllib.parse import urljoin

import requests

BASE_URL = "https://www.scrapestorm.net"
ENDPOINT = "/api/v2/linkedin.com/profile/posts-metrics-by-username"
HEADERS = {"Accept": "application/json", "X-API-Key": "00000000-0000-4000-8000-000000000000"}

params = {
    "username": "value",
}

with requests.Session() as session:
    response = session.request(
        method="GET",
        url=urljoin(BASE_URL, ENDPOINT),
        headers=HEADERS,
        params=params,
        timeout=30,
    )
    response.raise_for_status()
    payload = response.json()

print(payload)

const BASE_URL = "https://www.scrapestorm.net";
const endpoint = "/api/v2/linkedin.com/profile/posts-metrics-by-username";

const params = new URLSearchParams({
  username: "value",
});

const response = await fetch(`${BASE_URL}${endpoint}?${params.toString()}`, {
  method: "GET",
  headers: {
    Accept: "application/json",
    "X-API-Key": "00000000-0000-4000-8000-000000000000",
  },
});

if (!response.ok) {
  throw new Error(`Request failed: ${response.status} ${response.statusText}`);
}

const payload = await response.json();
console.log(payload);

import axios from "axios";

const client = axios.create({
  baseURL: "https://www.scrapestorm.net",
  timeout: 30000,
  headers: {
    Accept: "application/json",
    "X-API-Key": "00000000-0000-4000-8000-000000000000",
  },
});

const params = {
  username: "value",
};

const { data: payload } = await client.request({
  method: "GET",
  url: endpoint,
  params,
});

console.log(payload);

<?php

declare(strict_types=1);

use GuzzleHttp\Client;
use GuzzleHttp\Exception\GuzzleException;

$client = new Client([
    'base_uri' => "https://www.scrapestorm.net",
    'timeout' => 30.0,
    'headers' => [
        'Accept' => 'application/json',
        'X-API-Key' => "00000000-0000-4000-8000-000000000000",
    ],
]);

$query = [
    "username" => "value",
];

try {
    $response = $client->request("GET", "/api/v2/linkedin.com/profile/posts-metrics-by-username", [
        'query' => $query,
    ]);

    $payload = json_decode(
        (string) $response->getBody(),
        true,
        512,
        JSON_THROW_ON_ERROR
    );

    var_dump($payload);
} catch (GuzzleException $e) {
    throw $e;
}

package main

import (
    "encoding/json"
    "fmt"
    "net/http"
    "net/url"
    "time"
)

func main() {
    baseURL := "https://www.scrapestorm.net"
    endpoint := "/api/v2/linkedin.com/profile/posts-metrics-by-username"

    params := url.Values{}
    params.Set("username", "value")

    req, err := http.NewRequest(
        "GET",
        fmt.Sprintf("%s%s?%s", baseURL, endpoint, params.Encode()),
        nil,
    )
    if err != nil {
        panic(err)
    }

    req.Header.Set("Accept", "application/json")
    req.Header.Set("X-API-Key", "00000000-0000-4000-8000-000000000000")

    client := &http.Client{Timeout: 30 * time.Second}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    var payload any
    if err := json.NewDecoder(resp.Body).Decode(&payload); err != nil {
        panic(err)
    }

    fmt.Printf("%+v\n", payload)
}

Response example

Live response by version

The preview keeps key fields and the first collection items so you can scan the response shape quickly. Switching versions changes the JSON format.

Response example

V2 response JSON

Verified example

This compact JSON example comes from the latest successful verification run for V2.

{
  "success": true,
  "status": "ok",
  "search_context": {
    "username": "satyanadella"
  },
  "data": {
    "user": {
      "user_id": "19186432",
      "username": "satyanadella",
      "public_identifier": "satyanadella",
      "first_name": "Satya",
      "last_name": "Nadella",
      "full_name": "Satya Nadella",
      "profile_url": "https://www.linkedin.com/in/satyanadella",
      "headline": "Chairman and CEO at Microsoft",
      "summary": "As chairman and CEO of Microsoft, I define my mission and that of my company as empowering every person and every organization on the planet to achieve more.",
      "location": "Redmond, Washington, United States",
      "follower_count": 12000000,
      "connection_count": 500,
      "avatar_url": "https://example.com/image.jpg",
      "banner_url": "https://media.licdn.com/dms/image/v2/D5616AQFVwYcBLAcPqQ/profile-displaybackgroundimage-shrink_200_800/B56Z6tkWeBKAAQ-/0/1781028448390"
    },
    "analytics": {
      "all_posts": {
        "analyzed_posts_count": 3,
        "last_post_date": "2026-07-12T15:17:03.816000+00:00",
        "total_engagement": 8023,
        "avg_engagement_rate_per_post": 0.022286,
        "peak_engagement_rate_per_post": 0.025833,
        "avg_weighted_engagement_score": 2894.666667,
        "total_engagement_rate": 0.066858,
        "median_engagement_per_post": 2568.0,
        "max_engagement_per_post": 3100,
        "avg_caption_length": 272,
        "avg_posts_per_week": 1,
        "avg_posts_per_month": 2,
        "posts_count_last_7_days": 0,
        "posts_count_last_30_days": 2,
        "total_reactions": 7362,
        "total_comments": 661,
        "total_reposts": 0,
        "avg_reactions_per_post": 2454,
        "avg_comments_per_post": 220,
        "avg_reposts_per_post": 0,
        "total_reaction_rate": 0.06135,
        "total_comment_rate": 0.005508,
        "total_repost_rate": 0.0,
        "follower_count": 12000000,
        "_more_fields": "4 more fields"
      },
      "sponsored_posts": {
        "analyzed_posts_count": 0,
        "total_engagement": 0,
        "avg_engagement_rate_per_post": 0.0,
        "peak_engagement_rate_per_post": 0.0,
        "avg_weighted_engagement_score": 0.0,
        "total_engagement_rate": 0.0,
        "median_engagement_per_post": 0.0,
        "max_engagement_per_post": 0,
        "avg_caption_length": 0,
        "avg_posts_per_week": 0,
        "avg_posts_per_month": 0,
        "posts_count_last_7_days": 0,
        "posts_count_last_30_days": 0,
        "follower_count": 12000000
      },
      "organic_posts": {
        "analyzed_posts_count": 3,
        "last_post_date": "2026-07-12T15:17:03.816000+00:00",
        "total_engagement": 8023,
        "avg_engagement_rate_per_post": 0.022286,
        "peak_engagement_rate_per_post": 0.025833,
        "avg_weighted_engagement_score": 2894.666667,
        "total_engagement_rate": 0.066858,
        "median_engagement_per_post": 2568.0,
        "max_engagement_per_post": 3100,
        "avg_caption_length": 272,
        "avg_posts_per_week": 1,
        "avg_posts_per_month": 2,
        "posts_count_last_7_days": 0,
        "posts_count_last_30_days": 2,
        "total_reactions": 7362,
        "total_comments": 661,
        "total_reposts": 0,
        "avg_reactions_per_post": 2454,
        "avg_comments_per_post": 220,
        "avg_reposts_per_post": 0,
        "total_reaction_rate": 0.06135,
        "total_comment_rate": 0.005508,
        "total_repost_rate": 0.0,
        "follower_count": 12000000,
        "_more_fields": "4 more fields"
      },
      "segment_comparison": {
        "sponsored_content_share": 0.0,
        "organic_content_share": 100.0,
        "organic_vs_sponsored_engagement_rate_gap": 0.0223,
        "sponsored_to_organic_avg_engagement_ratio": 0.0
      }
    },
    "feed": {
      "count": 3,
      "items": [
        {
          "url": "https://www.linkedin.com/posts/satyanadella_the-reverse-information-paradox-activity-7482090659898630144-J4sB",
          "created_at": "2026-07-12T15:17:03.816Z",
          "post_id": "7482090659898630144",
          "entity_urn": "urn:li:activity:7482090659898630144",
          "text": "Some thoughts on the Reverse Information Paradox. https://lnkd.in/g-QKwksS",
          "author": {
            "url": "https://www.linkedin.com/in/satyanadella",
            "name": "Satya Nadella",
            "author_type": "user"
          },
          "reaction_count": 2300,
          "comment_count": 268,
          "is_sponsored": false,
          "sponsored_detection_source": null,
          "sponsored_detection_confidence": null
        },
        {
          "url": "https://www.linkedin.com/posts/satyanadella_microsoft-frontier-company-ai-engineering-activity-7478474505619726337-ge7_",
          "created_at": "2026-07-02T15:47:45.459Z",
          "post_id": "7478474505619726337",
          "entity_urn": "urn:li:activity:7478474505619726337",
          "text": "The future of the firm is a learning loop in which human capital and token capital compound. \n \nWith our new Frontier Co., our ambition is to help every enterprise build its own…",
          "author": {
            "url": "https://www.linkedin.com/in/satyanadella",
            "name": "Satya Nadella",
            "author_type": "user"
          },
          "reaction_count": 2876,
          "comment_count": 224,
          "is_sponsored": false,
          "sponsored_detection_source": null,
          "sponsored_detection_confidence": null
        },
        {
          "_more_items": 1
        }
      ]
    }
  }
}

Related methods

Continue working with Profile

Adjacent methods let you resolve the same object with another identifier, open details, or move to an aggregate view.

What to do next

Continue the evaluation

Use this documentation as the first decision point, then move into pricing, platform coverage, and integration rules before you connect the endpoint for recurring use.

Open the LinkedIn platform page

Compare adjacent entities, API method groups, and related docs before implementation.

Open platform page

Compare API method pricing

Check where this API method sits inside the public price table before you scale usage.

View pricing

Review integration rules

Use the starter docs to confirm authentication, versioning, retries, and mock vs live behavior.

Open docs

FAQ

Questions teams ask before implementation

Use these answers to decide whether this API method fits your workflow, versioning choice, and rollout plan.

What data does this LinkedIn API method return?

The method performs “Post metrics by username” for Profile. The compact response example below shows the exact field structure.

Should I choose V1 or V2?

Choose V2 for new integrations because it provides a normalized structure. Use V1 only for compatibility with clients that already consume the platform-native format.

What do I need for the first request?

Create an API key, send it in the request header, and provide the required parameters from the table. The code samples already contain the correct path and request structure.