> ## 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. # Preview Social Selling engager export > Preview exporting Social Selling engagers (people who reacted to or commented on the caller’s tracked LinkedIn posts) to a contacts list, without creating anything. Select engagers with `prospectIds` (from the engagers lists), with `postId` (a tracked post id, not `publishingPostId`), or with `dateFrom`/`dateTo` (UTC days of post publication) optionally narrowed by `identityIds`; then `interaction` (all, commented, reacted) and `contacts` (`new` = not yet in Enginy). The caller’s own identities and blocklisted people are never exported. Returns how many engagers the export would add (`prospectCount`), the LinkedIn enrichment price per contact, the credit estimate when `scrapeFromLinkedIn` is true (an upper bound), the credits available to the caller, and whether the export would be refused for lack of credits. One export takes at most 5000 engagers. Read-only: call it before the export to confirm the size and cost with the user. > **Required scope:** `SOCIAL_SELLING_READ` > > **Rate limit:** 100 requests per minute ## OpenAPI ````yaml https://openapi.enginy.ai/definitions.json post /v1/social-selling/engagers/export-preview 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/export-preview: post: tags: - Social Selling summary: Preview Social Selling engager export description: >- Preview exporting Social Selling engagers (people who reacted to or commented on the caller’s tracked LinkedIn posts) to a contacts list, without creating anything. Select engagers with `prospectIds` (from the engagers lists), with `postId` (a tracked post id, not `publishingPostId`), or with `dateFrom`/`dateTo` (UTC days of post publication) optionally narrowed by `identityIds`; then `interaction` (all, commented, reacted) and `contacts` (`new` = not yet in Enginy). The caller’s own identities and blocklisted people are never exported. Returns how many engagers the export would add (`prospectCount`), the LinkedIn enrichment price per contact, the credit estimate when `scrapeFromLinkedIn` is true (an upper bound), the credits available to the caller, and whether the export would be refused for lack of credits. One export takes at most 5000 engagers. Read-only: call it before the export to confirm the size and cost with the user. > **Required scope:** `SOCIAL_SELLING_READ` > > **Rate limit:** 100 requests per minute requestBody: content: application/json: schema: type: object properties: prospectIds: type: array items: type: integer exclusiveMinimum: 0 minItems: 1 maxItems: 1000 description: >- Export exactly these engagers (`prospectId` from the engagers lists), 1–1000. Do not combine with `postId`, `dateFrom`/`dateTo` or `identityIds`. example: - 5101 - 5102 postId: type: integer exclusiveMinimum: 0 description: >- Filter: every engager of this tracked post (`id` from the posts list, not `publishingPostId`). Wins over `dateFrom`/`dateTo`. dateFrom: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-09-01' description: >- Filter: engagers of the posts published from this day (UTC, inclusive). Required with `dateTo` unless `postId` is set. dateTo: type: string pattern: ^\d{4}-\d{2}-\d{2}$ example: '2026-09-01' description: >- Filter: engagers of the posts published until this day (UTC, inclusive). identityIds: type: array items: type: integer exclusiveMinimum: 0 minItems: 1 maxItems: 500 description: >- Filter: only engagers of these identities’ posts. Defaults to every identity the caller may see; ids outside that scope match nothing. interaction: type: string enum: - all - commented - reacted default: all description: >- Which engagers: `all`, only those who `commented`, or only those who `reacted`. contacts: type: string enum: - all - new default: all description: >- `new` keeps only engagers that are not contacts in Enginy yet. scrapeFromLinkedIn: type: boolean default: false description: >- Enrich every exported contact with LinkedIn profile data after the export. Costs `creditsPerContact` credits per enriched contact; off by default. responses: '200': description: What the export would do content: application/json: schema: type: object properties: status: type: string enum: - success message: type: string data: type: object properties: prospectCount: type: number description: >- Engagers the export would add (the caller’s own identities and blocklisted people excluded). scrapeFromLinkedIn: type: boolean creditsPerContact: type: number description: Credits one LinkedIn enrichment costs this workspace. estimatedCredits: type: number description: >- Upper bound of the credits the export spends: `prospectCount × creditsPerContact` when enriching, else 0. availableCredits: type: number description: >- Credits the export’s credit check compares against (the user’s monthly cap applied). wouldExceedBalance: type: boolean description: >- True when the export would be refused for insufficient credits. required: - prospectCount - scrapeFromLinkedIn - creditsPerContact - estimatedCredits - availableCredits - wouldExceedBalance required: - status - message - data '400': description: >- Invalid selection: `prospectIds` mixed with filter fields, more than 1000 ids, only one of `dateFrom`/`dateTo`, a day that does not exist, a reversed range, or no selection at all '403': description: >- Social Selling is not enabled for this workspace. Ask your workspace admin to enable the feature. '404': description: >- `postId` is not a tracked post of this workspace visible to the caller 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.