> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tweet-catcher.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Bulk Stop Tasks

> Stops up to 200 tasks by ID. Progress is streamed back via **Server-Sent Events** — one `progress` event per task, followed by `done` (or `error` on a fatal failure)



## OpenAPI

````yaml /api-specification.yaml post /bulk-stop-tasks
openapi: 3.0.3
info:
  title: Tweet Catcher Monitor API
  description: API for managing Tweet Catcher monitoring tasks and user data
  version: 1.0.0
  contact:
    name: Tweet Catcher
    url: https://dashboard.tweet-catcher.com/support
servers:
  - url: https://monitor-api.tweet-catcher.com/pro
    description: Production server
security:
  - ApiKeyToken: []
tags:
  - name: Manage Tasks
    description: Operations for managing Tweet Catcher monitoring tasks
  - name: User Data
    description: Operations for retrieving user-related data and history
paths:
  /bulk-stop-tasks:
    post:
      tags:
        - Manage Tasks
      summary: Bulk Stop Tasks
      description: >-
        Stops up to 200 tasks by ID. Progress is streamed back via **Server-Sent
        Events** — one `progress` event per task, followed by `done` (or `error`
        on a fatal failure)
      operationId: bulkStopTasks
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: array
              items:
                type: number
                nullable: true
              minItems: 1
              maxItems: 200
              description: Array of task IDs
              example:
                - 932
                - 933
                - 934
            example:
              - 932
              - 933
              - 934
      responses:
        '200':
          description: >-
            SSE stream — tasks are stopped sequentially; each result is emitted
            as a `progress` event
          content:
            text/event-stream:
              schema:
                type: string
                description: >-
                  A **Server-Sent Events (SSE)** stream (`Content-Type:
                  text/event-stream`).


                  The connection stays open while tasks are processed. Three
                  named event types are sent:


                  | Event      | When                             | Data
                  shape                 |

                  |------------|----------------------------------|----------------------------|

                  | `progress` | After each task is processed     | `{ index,
                  total, result }` |

                  | `done`     | All tasks finished successfully  | `{ total
                  }`                |

                  | `error`    | Fatal error aborts the operation | `{ error:
                  true, message }` |


                  Example stream:

                  ```

                  event: progress

                  data: {"index":0,"total":3,"result":{"error":false,"id":932}}


                  event: progress

                  data:
                  {"index":1,"total":3,"result":{"error":true,"message":"Task
                  limit reached"}}


                  event: done

                  data: {"total":3}

                  ```
                example: |+
                  event: progress
                  data: {"index":0,"total":3,"result":{"error":false}}

                  event: done
                  data: {"total":3}

                externalDocs:
                  description: MDN — Server-Sent Events
                  url: >-
                    https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events
        '400':
          description: Invalid request parameters (stream never opened)
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: boolean
                    example: true
                    description: Whether an error occurred
                  message:
                    type: string
                    example: Error message
                    description: The error message
                  errors:
                    type: object
                    additionalProperties:
                      type: array
                      items:
                        type: string
                    example:
                      email:
                        - Invalid module
                    description: The errors
                required:
                  - error
                  - message
              example:
                error: true
                message: Invalid request parameters
        '401':
          description: Authentication failed
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: boolean
                    example: true
                    description: Whether an error occurred
                  message:
                    type: string
                    example: Error message
                    description: The error message
                required:
                  - error
                  - message
              example:
                error: true
                message: Invalid or missing authorization token
        '500':
          description: Server error
      security:
        - ApiKeyToken: []
components:
  securitySchemes:
    ApiKeyToken:
      type: apiKey
      in: header
      name: Authorization
      description: Api key for application authentication

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.