> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enginy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# List Social Selling identity performance

> Rank the caller’s Social Selling identities (LinkedIn profiles) by performance over a date range: posts, impressions, reactions, comments, people reached and new people reached per identity, highest `sort` metric first. Same rows as the identities table of the Social Selling Overview page. Defaults to the last 30 days; only completed UTC days count. Read-only.

Responses include direct Enginy app URLs when available. Each identity includes an `appUrl` that opens its Social Selling page in Enginy. MCP agents should return those URLs to users whenever they are present in the response.

    > **Required scope:** `SOCIAL_SELLING_READ`
    >
    > **Rate limit:** 100 requests per minute



## OpenAPI

````yaml https://openapi.enginy.ai/definitions.json get /v1/social-selling/analytics/identities
openapi: 3.1.0
info:
  title: Enginy API
  version: 1.0.0
  description: Public API for Enginy platform
servers:
  - url: https://openapi.enginy.ai
    description: Configured server
security: []
tags:
  - name: AI Variables
    description: >-
      Manage AI variables and discover the entity fields you can reference in
      prompts and entity requests.
  - name: Inbox
    description: >-
      Inbox endpoints for listing contact threads, reading thread messages,
      managing tags, and sending manual replies.
  - name: Workflows
    description: >-
      Build, validate, publish, run, and inspect advanced (graph) workflows,
      plus the block/condition catalog needed to author a workflow plan.
paths:
  /v1/social-selling/analytics/identities:
    get:
      tags:
        - Social Selling
      summary: List Social Selling identity performance
      description: >-
        Rank the caller’s Social Selling identities (LinkedIn profiles) by
        performance over a date range: posts, impressions, reactions, comments,
        people reached and new people reached per identity, highest `sort`
        metric first. Same rows as the identities table of the Social Selling
        Overview page. Defaults to the last 30 days; only completed UTC days
        count. Read-only.


        Responses include direct Enginy app URLs when available. Each identity
        includes an `appUrl` that opens its Social Selling page in Enginy. MCP
        agents should return those URLs to users whenever they are present in
        the response.

            > **Required scope:** `SOCIAL_SELLING_READ`
            >
            > **Rate limit:** 100 requests per minute
      parameters:
        - schema:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}$
            example: '2026-09-01'
            description: First day (UTC, inclusive). Defaults to 30 days before `dateTo`.
          required: false
          description: First day (UTC, inclusive). Defaults to 30 days before `dateTo`.
          name: dateFrom
          in: query
        - schema:
            type: string
            pattern: ^\d{4}-\d{2}-\d{2}$
            example: '2026-09-01'
            description: >-
              Last day (UTC, inclusive). Defaults to today. At most 366 days in
              total. Only completed days count: today (and yesterday before
              03:00 UTC) has no metrics yet.
          required: false
          description: >-
            Last day (UTC, inclusive). Defaults to today. At most 366 days in
            total. Only completed days count: today (and yesterday before 03:00
            UTC) has no metrics yet.
          name: dateTo
          in: query
        - schema:
            type:
              - array
              - 'null'
            items:
              type: integer
              exclusiveMinimum: 0
            minItems: 1
            description: >-
              List of identity ids to keep (REST also accepts a comma-separated
              value). Defaults to every identity the caller may see; ids outside
              that scope are ignored.
            example: 12,34
          required: false
          description: >-
            List of identity ids to keep (REST also accepts a comma-separated
            value). Defaults to every identity the caller may see; ids outside
            that scope are ignored.
          name: identityIds
          in: query
        - schema:
            type: string
            enum:
              - reached
              - impressions
              - reactions
              - comments
              - posts
            default: reached
            description: Metric to rank identities by, highest first.
          required: false
          description: Metric to rank identities by, highest first.
          name: sort
          in: query
      responses:
        '200':
          description: One row per identity with activity in the range, best first
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    type: string
                    enum:
                      - success
                  message:
                    type: string
                  data:
                    type: object
                    properties:
                      dateFrom:
                        type: string
                      dateTo:
                        type: string
                      sort:
                        type: string
                        enum:
                          - reached
                          - impressions
                          - reactions
                          - comments
                          - posts
                      identities:
                        type: array
                        items:
                          type: object
                          properties:
                            identityId:
                              type: number
                            label:
                              type: string
                            avatarUrl:
                              type:
                                - string
                                - 'null'
                            linkedInUrl:
                              type:
                                - string
                                - 'null'
                            posts:
                              type: number
                            impressions:
                              type: number
                            impressionsVerified:
                              type: boolean
                              description: >-
                                True when the impressions are LinkedIn’s own
                                analytics numbers.
                            reactions:
                              type: number
                            comments:
                              type: number
                            reached:
                              type: number
                            newReached:
                              type: number
                            appUrl:
                              type: string
                              description: >-
                                Opens the identity’s Social Selling page in
                                Enginy.
                          required:
                            - identityId
                            - label
                            - avatarUrl
                            - linkedInUrl
                            - posts
                            - impressions
                            - impressionsVerified
                            - reactions
                            - comments
                            - reached
                            - newReached
                            - appUrl
                    required:
                      - dateFrom
                      - dateTo
                      - sort
                      - identities
                required:
                  - status
                  - message
                  - data
        '400':
          description: >-
            Invalid query: a date that is not YYYY-MM-DD or a day that does not
            exist (`2026-02-30`), a range over 366 days or ending before it
            starts, or malformed identity ids, or an unknown `sort`
        '403':
          description: >-
            Social Selling is not enabled for this workspace. Ask your workspace
            admin to enable the feature.
      security:
        - apiKey: []
components:
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: x-api-key

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.