> ## Documentation Index > Fetch the complete documentation index at: https://docs.clustr-ai.com/llms.txt > Use this file to discover all available pages before exploring further. # Export Account Interactions > Every competitor interaction touching one account, as JSON or CSV Every competitor interaction touching **one** account, in one response: the same rows as [List Account Interactions](https://docs.clustr-ai.com/api-reference/list-account-competitor-interactions.md), ready to open in a spreadsheet. Interactions you ignored are left out. `accountID` is the account's [Clustr ID](https://docs.clustr-ai.com/clustr-ids.md). The company's LinkedIn numeric id works too: the `company_numeric_id` that [List Competitor Accounts](https://docs.clustr-ai.com/api-reference/list-competitor-accounts.md) returns. The file works like the [workspace-wide export](https://docs.clustr-ai.com/api-reference/export-competitor-interactions.md): add `format=csv` for a CSV file, read `X-Export-Total`, `X-Export-Rows` and `X-Export-Truncated` for its size, and send `Accept-Encoding: gzip` for a smaller response. ```bash cURL theme={null} curl --compressed -OJ "https://api.clustr-ai.com/api/public/competitor-accounts/acc_2mhxbznjtvpympw45ng1m3333c/interactions/export?format=csv" \ -H "Authorization: Bearer YOUR_API_KEY" ``` ## OpenAPI ````yaml GET /competitor-accounts/{accountID}/interactions/export openapi: 3.1.0 info: title: Clustr Public API description: > Programmatic access to your Clustr network: import connectors, search warm intros (opportunities), and manage target accounts. ## Authentication All endpoints require a Bearer token (API key) in the `Authorization` header. ``` Authorization: Bearer ``` API keys can be created and managed from the [API settings page](https://app.clustr-ai.com/api). version: '1.0' contact: name: Clustr Support url: https://clustr-ai.com servers: - url: https://api.clustr-ai.com/api/public description: Production security: - BearerAuth: [] paths: /competitor-accounts/{accountID}/interactions/export: get: tags: - Competitor Monitoring summary: Export Account Interactions description: >- Exports every competitor interaction touching one account in one response, ready to open in a spreadsheet. It holds the same interactions as List Account Interactions, leaving out the ones you ignored, with the CRM owner and open-deal columns read from your CRM at export time. The export works like Export Competitor Interactions: add `format=csv` for a CSV file, read the `X-Export-Total`, `X-Export-Rows` and `X-Export-Truncated` headers for its size (at most 50,000 interactions), and send `Accept-Encoding: gzip` for a smaller response. operationId: exportAccountInteractions parameters: - name: accountID in: path required: true description: >- The account's Clustr ID (`acc_…`). Its LinkedIn numeric company id, the `company_numeric_id` that [List Competitor Accounts](/api-reference/list-competitor-accounts) returns, also works. schema: type: string example: acc_2q86syry378nwfwnjgk4q6ane1 - name: format in: query required: false description: > `json` (the default) or `csv`. CSV is UTF-8 with a byte order mark, served as an attachment named `clustr-competitor-interactions-.csv`; a cell that starts with = + - @ gets a leading apostrophe so a spreadsheet reads it as text. schema: type: string enum: - json - csv default: json example: csv responses: '200': description: The account's interactions headers: X-Export-Total: description: The number of interactions on this account. schema: type: integer X-Export-Rows: description: The number of interactions in this response, at most 50,000. schema: type: integer X-Export-Truncated: description: >- `true` when the account holds more interactions than this response. schema: type: boolean Content-Disposition: description: The file name, on a CSV response. schema: type: string content: text/csv: schema: type: string description: The CSV file, when `format=csv`. application/json: schema: type: object required: - success - data properties: success: type: boolean example: true data: type: object properties: interactions: type: array items: type: object additionalProperties: true total: type: integer example: 14 truncated: type: boolean example: false example: success: true data: interactions: - clustr_competitor_id: cmp_r0jpyyqyeh0txpgdhb604j2g9s clustr_rep_person_id: per_wdkt5r93eezq6vj1mb4tdn1x1r clustr_target_person_id: per_0fb2mgv9x1fbs2kdzv4gt2j88n competitor_id: c1a2b3c4-d5e6-7890-abcd-ef1234567890 competitor_name: Rival Inc competitor_domain: rival.com rep_linkedin_id: ACoAAB1x2y3z rep_name: Jordan Lee rep_title: Account Executive target_linkedin_id: ACoAAC4d5e6f target_name: Marie Dubois target_job_title: Head of Operations interaction_type: comment engagement_at: '2026-10-08T09:14:00Z' content_preview: >- Happy to show you how we solved this for teams like yours. post_url: >- https://www.linkedin.com/feed/update/urn:li:activity:7250000000000000000 target_company_name: Acme Corp target_company_domain: acme.com owner_name: Alice Martin owner_email: alice@company.com has_open_deal: true deal_name: Acme renewal 2027 deal_stage: negotiation deal_amount: 48000 is_customer: true is_target: false we_know_target: true is_pitch: true total: 1 truncated: false '400': description: '`format` is neither `json` nor `csv`' content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Invalid or missing API key '403': description: Competitor monitoring is not enabled for this workspace content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' components: schemas: ErrorResponse: type: object required: - success - error properties: success: type: boolean example: false error: type: object properties: message: type: string example: Invalid request body code: type: string example: BAD_REQUEST securitySchemes: BearerAuth: type: http scheme: bearer description: The API key you created on the API settings page of the Clustr app. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.