# Bulk reconnect email accounts

## OpenAPI Specification

```yaml
openapi: 3.0.1
info:
  title: ''
  description: ''
  version: 1.0.0
paths:
  /account/bulk-reconnect:
    post:
      summary: Bulk reconnect email accounts
      deprecated: false
      description: >-
        Reconnecting only works if account credentials haven't changed (e.g., a
        temporary error or bounce).

        Google and Microsoft accounts: This usually won’t work — you’ll need to
        reconnect manually.

        Only try once. Repeated attempts are unlikely to help and may cause
        further issues.
      operationId: bulkReconnectEmailAccounts
      tags:
        - Email Account
        - Email Accounts
      parameters:
        - name: x-api-key
          in: header
          description: Your PlusVibe.ai account's API Key
          required: true
          example: ''
          schema:
            type: string
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                workspace_id:
                  type: string
                ids:
                  type: array
                  items:
                    type: string
              required:
                - workspace_id
                - ids
              x-apidog-orders:
                - workspace_id
                - ids
              x-apidog-ignore-properties: []
            example:
              ids:
                - 68329272b5658177e8e4c620
              workspace_id: 65f3c92d3dbe5dbb35374a9a
      responses:
        '200':
          description: Email accounts successfully reconnected
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessResponse'
              example:
                status: success
          headers: {}
          x-apidog-name: OK
        '400':
          description: Bad request - Invalid input parameters
          content:
            application/json:
              schema: &ref_0
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                '2':
                  summary: Validation error
                  value:
                    message: Validation error
                    error: Validation error
                    errors:
                      - campaign_id must be a valid 24 character hex string
                '3':
                  summary: Resource not found
                  value:
                    message: Campaign not found
                    error: The specified campaign does not exist
          headers: {}
          x-apidog-name: Bad Request
        '401':
          description: Unauthorized - Invalid API key
          content:
            application/json:
              schema: *ref_0
              example:
                message: Invalid API key
                error: Unauthorized access
          headers: {}
          x-apidog-name: Unauthorized
        '403':
          description: Forbidden - Insufficient permissions
          content:
            application/json:
              schema: *ref_0
              example:
                message: Insufficient permissions
                error: Access denied
          headers: {}
          x-apidog-name: Forbidden
        '500':
          description: Internal server error
          content:
            application/json:
              schema: *ref_0
              example:
                message: Internal server error occurred
                error: Database connection failed
          headers: {}
          x-apidog-name: Server Error
      security: []
      x-apidog-folder: Email Account
      x-apidog-status: released
      x-run-in-apidog: https://app.apidog.com/web/project/929054/apis/api-21411385-run
components:
  schemas:
    SuccessResponse:
      type: object
      properties:
        status:
          type: integer
          examples:
            - 1
        message:
          type: string
          examples:
            - Operation successful
        data:
          type: object
          x-apidog-orders: []
          properties: {}
          x-apidog-ignore-properties: []
      x-apidog-orders:
        - status
        - message
        - data
      x-apidog-ignore-properties: []
      x-apidog-folder: ''
    ErrorResponse:
      type: object
      required:
        - code
        - message
        - data
      properties:
        code:
          type: integer
          enum:
            - 0
        message:
          type: string
        data:
          type: object
          x-apidog-orders: []
          properties: {}
          x-apidog-ignore-properties: []
      x-apidog-orders:
        - code
        - message
        - data
      x-apidog-ignore-properties: []
      x-apidog-folder: ''
  securitySchemes:
    ApiKeyAuth:
      type: apikey
      in: header
      name: x-api-key
      description: |
        API key issued in the PlusVibe dashboard. The server reads it
        from the `x-api-key` header and injects it into the request as
        the `api_key` query parameter, which is why you will see
        `api_key` referenced in validation errors.
    apiKey:
      type: apikey
      in: body
      name: api_key
      description: API key passed in request body
servers:
  - url: https://api.plusvibe.ai/api/v1
    description: Prod Env
security:
  - ApiKeyAuth: []
    x-apidog:
      schemeGroups:
        - id: uS5KiuC4wfZHK42AzOfA_
          schemeIds:
            - ApiKeyAuth
      required: true
      use:
        id: uS5KiuC4wfZHK42AzOfA_
      scopes:
        uS5KiuC4wfZHK42AzOfA_:
          ApiKeyAuth: []

```