> ## 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 engagers > List the people (engagers) who reacted to or commented on LinkedIn posts the caller’s Social Selling identities published in a date range — the Prospects page of Social Selling. Each row has the engager’s profile, whether they are already an Enginy contact (`contactStatus`: NEW, IN_CRM, CONTACTED; `contactId`), their interactions on the range’s posts and their lifetime engagement score. The rows and the in-range counts cover the caller’s identities only. `engagementScore` and `totalInteractions` count every identity of the workspace, including identities the caller cannot see, as on the Prospects page. `firstInteractionAt`/`lastInteractionAt` are when an Enginy sync first/last detected the person on any tracked post of the workspace, not when they engaged. Filter by contact status, interaction kind, company or minimum (workspace-wide) score; sort and page server-side. Blocklisted people and the workspace’s own identities never appear. `prospectId` is what the engager export tools take. Defaults to posts of the last 90 days. Read-only. Responses include direct Enginy app URLs when available. Engagers already in the CRM include a `contactAppUrl` that opens the contact 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/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/engagers: get: tags: - Social Selling summary: List Social Selling engagers description: >- List the people (engagers) who reacted to or commented on LinkedIn posts the caller’s Social Selling identities published in a date range — the Prospects page of Social Selling. Each row has the engager’s profile, whether they are already an Enginy contact (`contactStatus`: NEW, IN_CRM, CONTACTED; `contactId`), their interactions on the range’s posts and their lifetime engagement score. The rows and the in-range counts cover the caller’s identities only. `engagementScore` and `totalInteractions` count every identity of the workspace, including identities the caller cannot see, as on the Prospects page. `firstInteractionAt`/`lastInteractionAt` are when an Enginy sync first/last detected the person on any tracked post of the workspace, not when they engaged. Filter by contact status, interaction kind, company or minimum (workspace-wide) score; sort and page server-side. Blocklisted people and the workspace’s own identities never appear. `prospectId` is what the engager export tools take. Defaults to posts of the last 90 days. Read-only. Responses include direct Enginy app URLs when available. Engagers already in the CRM include a `contactAppUrl` that opens the contact 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 publication day (UTC) of the posts engaged with. Defaults to 89 days before `dateTo`. required: false description: >- First publication day (UTC) of the posts engaged with. Defaults to 89 days before `dateTo`. name: dateFrom in: query - schema: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-09-01' description: >- Last publication day (UTC, inclusive). Defaults to today. At most 366 days in total. required: false description: >- Last publication day (UTC, inclusive). Defaults to today. At most 366 days in total. name: dateTo in: query - schema: type: - array - 'null' items: type: integer exclusiveMinimum: 0 minItems: 1 description: >- List of identity ids whose posts count (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 whose posts count (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: - array - 'null' items: type: string enum: - NEW - IN_CRM - CONTACTED minItems: 1 description: >- List of contact statuses to keep (REST also accepts a comma-separated value): NEW (not in Enginy), IN_CRM (an Enginy contact not contacted yet), CONTACTED. example: NEW,IN_CRM required: false description: >- List of contact statuses to keep (REST also accepts a comma-separated value): NEW (not in Enginy), IN_CRM (an Enginy contact not contacted yet), CONTACTED. name: contactStatus in: query - schema: type: string enum: - all - reacted - commented default: all description: >- `reacted` / `commented`: only engagers with a reaction / comment on those posts. required: false description: >- `reacted` / `commented`: only engagers with a reaction / comment on those posts. name: interaction in: query - schema: type: string minLength: 1 maxLength: 200 description: Case-insensitive part of the engager’s current company name. required: false description: Case-insensitive part of the engager’s current company name. name: company in: query - schema: type: - number - 'null' minimum: 0 description: >- Keep engagers whose lifetime `engagementScore` is at least this. That score counts every identity of the workspace, including identities the caller cannot see. required: false description: >- Keep engagers whose lifetime `engagementScore` is at least this. That score counts every identity of the workspace, including identities the caller cannot see. name: minEngagementScore in: query - schema: type: string enum: - engagementScore - interactions - reactions - comments default: engagementScore description: >- Highest first. `engagementScore` is the workspace-wide lifetime score; `interactions`/`reactions`/`comments` count the range’s posts of the caller’s identities only. required: false description: >- Highest first. `engagementScore` is the workspace-wide lifetime score; `interactions`/`reactions`/`comments` count the range’s posts of the caller’s identities only. name: sort in: query - schema: type: integer minimum: 1 default: 1 required: false name: page in: query - schema: type: integer minimum: 1 maximum: 100 default: 25 required: false name: pageSize in: query responses: '200': description: Paginated engagers content: application/json: schema: type: object properties: data: 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' contactStatus: type: string enum: - NEW - IN_CRM - CONTACTED engagementScore: type: number description: >- Lifetime engagement score (not limited to the range). It counts every identity of the workspace, including identities the caller cannot see, as on the Prospects page. reactionsInRange: type: number description: >- Reactions on the range’s posts of the caller’s identities. commentsInRange: type: number description: >- Comments on the range’s posts of the caller’s identities. interactionsInRange: type: number description: >- All interactions on the range’s posts of the caller’s identities. identitiesInRange: type: number description: >- How many of the caller’s identities they engaged with on the range’s posts. totalInteractions: type: number description: >- Lifetime interactions with any tracked post of the workspace, including posts of identities the caller cannot see. firstInteractionAt: type: string description: >- When an Enginy sync first detected this person on a tracked post of the workspace (any identity), not when they engaged. lastInteractionAt: type: string description: >- When an Enginy sync last detected this person on a tracked post of the workspace (any identity). Every sync that sees them again refreshes it, so it is not when they last engaged. contactAppUrl: type: - string - 'null' description: Opens the matching contact in Enginy. required: - prospectId - contactId - companyId - fullName - headline - company - linkedinProfileUrl - contactStatus - engagementScore - reactionsInRange - commentsInRange - interactionsInRange - identitiesInRange - totalInteractions - firstInteractionAt - lastInteractionAt - contactAppUrl meta: type: object properties: page: type: number pageSize: type: number total: type: number required: - page - pageSize - total required: - data - meta '400': description: >- Invalid query: a date that is not YYYY-MM-DD, a range over 366 days or ending before it starts, an unknown `contactStatus`/`interaction`/`sort`, or `pageSize` over 100 '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.