> ## 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 post engagers > List who engaged with one tracked LinkedIn post: one row per person with whether they reacted (and how), whether they commented (with the comment text) and whether they are already an Enginy contact (`contactStatus`, `contactId`). `postId` is the tracked post id from `list_social_selling_posts` (not a publishing post id). Includes LinkedIn’s totals for the post and how many engagers the workspace blocklist hides; the workspace’s own identities never appear. `prospectId` is what the engager export tools take. Read-only. Responses include direct Enginy app URLs when available. The post includes an `appUrl` that opens it in Enginy; engagers already in the CRM include a `contactAppUrl`. 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/posts/{postId}/engagers 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/posts/{postId}/engagers: get: tags: - Social Selling summary: List Social Selling post engagers description: >- List who engaged with one tracked LinkedIn post: one row per person with whether they reacted (and how), whether they commented (with the comment text) and whether they are already an Enginy contact (`contactStatus`, `contactId`). `postId` is the tracked post id from `list_social_selling_posts` (not a publishing post id). Includes LinkedIn’s totals for the post and how many engagers the workspace blocklist hides; the workspace’s own identities never appear. `prospectId` is what the engager export tools take. Read-only. Responses include direct Enginy app URLs when available. The post includes an `appUrl` that opens it in Enginy; engagers already in the CRM include a `contactAppUrl`. 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: integer exclusiveMinimum: 0 description: Tracked post id (`id` in the posts list). required: true description: Tracked post id (`id` in the posts list). name: postId in: path - schema: type: string enum: - all - reacted - commented default: all description: >- `reacted` / `commented`: only people who reacted to / commented on the post. required: false description: >- `reacted` / `commented`: only people who reacted to / commented on the post. name: interaction in: query - schema: type: integer minimum: 1 default: 1 required: false name: page in: query - schema: type: integer minimum: 1 maximum: 200 default: 50 required: false name: pageSize in: query responses: '200': description: The post, one page of its engagers and the page metadata content: application/json: schema: type: object properties: status: type: string enum: - success message: type: string data: type: object properties: post: type: object properties: id: type: number description: Tracked post id. publishingPostId: type: - number - 'null' identityId: type: number url: type: - string - 'null' postedAt: type: - string - 'null' totals: type: object properties: reactions: type: number reactionsByType: type: object additionalProperties: type: number comments: type: number required: - reactions - reactionsByType - comments description: >- LinkedIn’s own counters for the post (they include people we could not identify). hiddenBlockedCount: type: number description: >- Engagers left out because they match the workspace blocklist. appUrl: type: - string - 'null' description: >- Opens the post in Enginy (null until it has a publishing post). required: - id - publishingPostId - identityId - url - postedAt - totals - hiddenBlockedCount - appUrl engagers: type: array items: type: object properties: prospectId: type: number description: >- Engager id. Pass it to the export tools to add engagers to a contact list. contactId: type: - number - 'null' description: >- The matching Enginy contact, when already in the CRM. companyId: type: - number - 'null' description: The matching Enginy company, when known. fullName: type: - string - 'null' headline: type: - string - 'null' company: type: - string - 'null' linkedinProfileUrl: type: - string - 'null' reacted: type: boolean reactionType: type: - string - 'null' example: LIKE commented: type: boolean commentText: type: - string - 'null' commentUrn: type: - string - 'null' description: >- LinkedIn URN of their comment, when captured (needed to boost the comment). contactStatus: type: string enum: - NEW - IN_CRM - CONTACTED contactAppUrl: type: - string - 'null' description: Opens the matching contact in Enginy. required: - prospectId - contactId - companyId - fullName - headline - company - linkedinProfileUrl - reacted - reactionType - commented - commentText - commentUrn - contactStatus - contactAppUrl meta: type: object properties: page: type: number pageSize: type: number total: type: number required: - page - pageSize - total required: - post - engagers - meta required: - status - message - data '400': description: Invalid post id, unknown `interaction`, or `pageSize` over 200 '403': description: >- Social Selling is not enabled for this workspace. Ask your workspace admin to enable the feature. '404': description: >- Post not found in this workspace or outside the caller’s identity scope 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.