> ## 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.

# Ignore an Interaction

> Mark a competitor interaction as a false positive, for good

Ignore one or more competitor interactions for good. An ignored interaction never sends an alert and leaves every count: the [Attack and Defense lists](https://docs.clustr-ai.com/api-reference/list-competitor-accounts.md), the [account view](https://docs.clustr-ai.com/api-reference/get-competitor-account.md) and the competitor summaries. It works on any interaction, likes included.

History is kept. [Unignore](https://docs.clustr-ai.com/api-reference/unignore-competitor-interaction.md) brings an interaction back, and [the ignored list](https://docs.clustr-ai.com/api-reference/list-ignored-competitor-interactions.md) shows what you ignored.

Compare with the other two triage actions: [snooze](https://docs.clustr-ai.com/api-reference/snooze-competitor-interaction.md) hides one classified comment until a date, and [dismiss](https://docs.clustr-ai.com/api-reference/dismiss-competitor-target.md) silences a person, including interactions not collected yet. Ignore is one interaction, permanently.

Idempotent: ignoring an interaction twice keeps the first time and author.

Send one interaction as top-level fields, or several in `interactions`. Take the values from the interaction row ([account interactions](https://docs.clustr-ai.com/api-reference/list-account-competitor-interactions.md) or [the feed](https://docs.clustr-ai.com/api-reference/list-competitor-interactions.md)).

```bash cURL theme={null}
curl -X POST https://api.clustr-ai.com/api/public/competitor-interactions/ignore \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "actor_linkedin_id": "per_x3mj8hbn822n1xybc73f80s3em",
    "target_linkedin_id": "per_pfc2a7z0j6r9sbtedxy7gayf39",
    "post_key": "7381234567890123456",
    "interaction_type": "like"
  }'
```

```python Python theme={null}
import requests

requests.post(
    "https://api.clustr-ai.com/api/public/competitor-interactions/ignore",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={
        "actor_linkedin_id": "per_x3mj8hbn822n1xybc73f80s3em",
        "target_linkedin_id": "per_pfc2a7z0j6r9sbtedxy7gayf39",
        "post_key": "7381234567890123456",
        "interaction_type": "like",
    },
)
```

```javascript JavaScript theme={null}
await fetch("https://api.clustr-ai.com/api/public/competitor-interactions/ignore", {
  method: "POST",
  headers: { Authorization: "Bearer YOUR_API_KEY", "Content-Type": "application/json" },
  body: JSON.stringify({
    actor_linkedin_id: "per_x3mj8hbn822n1xybc73f80s3em",
    target_linkedin_id: "per_pfc2a7z0j6r9sbtedxy7gayf39",
    post_key: "7381234567890123456",
    interaction_type: "like",
  }),
});
```

```json 200 theme={null}
{
  "success": true,
  "data": { "ok": true, "ignored": 1 }
}
```


## OpenAPI

````yaml POST /competitor-interactions/ignore
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 <your_api_key>

    ```


    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-interactions/ignore:
    post:
      tags:
        - Competitor Monitoring
      summary: Ignore an Interaction
      description: >-
        Ignores one or more interactions. An ignored interaction stops alerting
        and drops out of every count in the Attack and Defense views. The
        interaction stays in your history, and Unignore an Interaction brings it
        back. Ignoring the same interaction twice has the same effect as once.
      operationId: ignoreCompetitorInteraction
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              description: >-
                One interaction as top-level fields, or several in
                `interactions`.
              properties:
                actor_linkedin_id:
                  type: string
                  description: >-
                    The interaction's `actor_key`, or the Clustr ID (`per_…`) of
                    its rep when it has no `actor_key`.

                    The rep's `rep_linkedin_id` also works.
                target_linkedin_id:
                  type: string
                  description: >-
                    The Clustr ID (`per_…`) of the person the interaction is
                    with. Their `target_linkedin_id` also

                    works.
                post_key:
                  type: string
                  description: >-
                    The interaction's `post_key`. Empty when the interaction has
                    none.
                interaction_type:
                  type: string
                  description: >-
                    The interaction's `interaction_type`, such as `comment` or
                    `like`. Leave it out to ignore every type of interaction
                    between the two people on that post.
                competitor_id:
                  type: string
                  description: >-
                    The competitor's Clustr ID (`cmp_…`), shown on the ignored
                    list. Optional. The id from earlier

                    responses also works.
                interactions:
                  type: array
                  description: >-
                    Several interactions at once, each with the fields above. At
                    most 500.
                  maxItems: 500
                  items:
                    type: object
                    required:
                      - actor_linkedin_id
                      - target_linkedin_id
                    properties:
                      actor_linkedin_id:
                        type: string
                        description: As `actor_linkedin_id` above.
                      target_linkedin_id:
                        type: string
                        description: As `target_linkedin_id` above.
                      post_key:
                        type: string
                      interaction_type:
                        type: string
                      competitor_id:
                        type: string
                        description: As `competitor_id` above.
      responses:
        '200':
          description: Done
          content:
            application/json:
              schema:
                type: object
                required:
                  - success
                  - data
                properties:
                  success:
                    type: boolean
                    example: true
                  data:
                    type: object
                    additionalProperties: true
        '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.