> ## 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. # Get Social Selling post outcomes > What happened with the people who engaged with one tracked post: for each external engager (blocklisted people excluded from rows and counts, teammates counted apart), whether they are an Enginy contact you may see, and the touchpoints that followed their first interaction within `windowDays` — first message sent and first reply of each conversation, meetings booked. Every touchpoint is INFERRED_TEMPORAL (it happened after the interaction); Enginy records no click or form event tied to a post, so nothing is DIRECT, and no deal data exists. Contacts behind several engager profiles count once. Read-only. Responses include direct Enginy app URLs when available. The post includes an `appUrl`; 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}/outcomes 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}/outcomes: get: tags: - Social Selling summary: Get Social Selling post outcomes description: >- What happened with the people who engaged with one tracked post: for each external engager (blocklisted people excluded from rows and counts, teammates counted apart), whether they are an Enginy contact you may see, and the touchpoints that followed their first interaction within `windowDays` — first message sent and first reply of each conversation, meetings booked. Every touchpoint is INFERRED_TEMPORAL (it happened after the interaction); Enginy records no click or form event tied to a post, so nothing is DIRECT, and no deal data exists. Contacts behind several engager profiles count once. Read-only. Responses include direct Enginy app URLs when available. The post includes an `appUrl`; 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: integer minimum: 1 maximum: 90 default: 30 description: >- Count touchpoints this many days after each person first engaged (1-90, default 30). required: false description: >- Count touchpoints this many days after each person first engaged (1-90, default 30). name: windowDays 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: >- Attribution method, summary and one page of engagers with their touchpoints 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 publishingPostId: type: - number - 'null' identityId: type: number postedAt: type: - string - 'null' appUrl: type: - string - 'null' required: - id - publishingPostId - identityId - postedAt - appUrl attribution: type: object properties: method: type: string enum: - INFERRED_TEMPORAL windowDays: type: number directEvidence: type: object properties: available: type: boolean enum: - false reason: type: string required: - available - reason required: - method - windowDays - directEvidence summary: type: object properties: externalEngagers: type: number internalEngagers: type: number blockedEngagersExcluded: type: number engagersInCrm: type: number contactsMessaged: type: number contactsReplied: type: number meetingsBooked: type: number deals: type: object properties: available: type: boolean enum: - false reason: type: string required: - available - reason truncated: type: boolean required: - externalEngagers - internalEngagers - blockedEngagersExcluded - engagersInCrm - contactsMessaged - contactsReplied - meetingsBooked - deals - truncated engagers: type: array items: type: object properties: prospectId: type: number fullName: type: - string - 'null' headline: type: - string - 'null' company: type: - string - 'null' linkedinProfileUrl: type: - string - 'null' interactions: type: array items: type: string enum: - REACTION - COMMENT firstInteractionAt: type: string contactId: type: - number - 'null' companyId: type: - number - 'null' contactAppUrl: type: - string - 'null' touchpoints: type: array items: type: object properties: type: type: string enum: - MESSAGE_SENT - REPLY_RECEIVED - MEETING_BOOKED occurredAt: type: string daysAfterInteraction: type: number attributionMethod: type: string enum: - DIRECT - INFERRED_TEMPORAL conversationId: type: - number - 'null' campaignId: type: - number - 'null' channel: type: - string - 'null' meetingId: type: - number - 'null' required: - type - occurredAt - daysAfterInteraction - attributionMethod - conversationId - campaignId - channel - meetingId required: - prospectId - fullName - headline - company - linkedinProfileUrl - interactions - firstInteractionAt - contactId - companyId - contactAppUrl - touchpoints meta: type: object properties: page: type: number pageSize: type: number total: type: number required: - page - pageSize - total required: - post - attribution - summary - engagers - meta required: - status - message - data '400': description: Invalid post id, `windowDays` outside 1-90 or `pageSize` over 100 '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.