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

# Delete connector by ID

> By default, soft-deletes a connector: the connector is marked as archived and will no longer ingest new content; existing documents that were ingested by this connector remain available. The operation is idempotent for an already-archived connector.

To permanently remove the connector and all related data, add the query parameter `force_delete=true`. This triggers a hard delete flow: all files related to this connector are deleted asynchronously. Once all files are deleted, the connector is removed from the database (final step of the async process). The deletion process is asynchronous.



## OpenAPI

````yaml /api-rest/openapi/openapi_content_data.json delete /contents/v1/connectors/{connector_id}
openapi: 3.1.0
info:
  title: Bigdata Content API
  description: API for managing and accessing private content documents uploaded by users.
  version: 1.0.0
servers:
  - url: https://api.bigdata.com/
security:
  - ApiKeyAuth: []
paths:
  /contents/v1/connectors/{connector_id}:
    delete:
      tags:
        - Connectors
      summary: Delete connector by ID
      description: >-
        By default, soft-deletes a connector: the connector is marked as
        archived and will no longer ingest new content; existing documents that
        were ingested by this connector remain available. The operation is
        idempotent for an already-archived connector.


        To permanently remove the connector and all related data, add the query
        parameter `force_delete=true`. This triggers a hard delete flow: all
        files related to this connector are deleted asynchronously. Once all
        files are deleted, the connector is removed from the database (final
        step of the async process). The deletion process is asynchronous.
      parameters:
        - name: connector_id
          in: path
          required: true
          description: >-
            UUID of the connector to archive or to hard-delete when
            force_delete=true.
          schema:
            type: string
            format: uuid
            example: 019a9612-bfad-758c-884e-37dd8c6ad2cb
        - name: force_delete
          in: query
          required: false
          description: >-
            If true, triggers a hard delete: all files related to this connector
            are deleted asynchronously, then the connector is removed from the
            database. If omitted or false, the connector is soft-deleted
            (archived) and existing documents remain.
          schema:
            type: boolean
            default: false
      responses:
        '200':
          description: >-
            Without force_delete: the connector object in its archived state; it
            will no longer accept new content and existing documents are
            unchanged. With force_delete=true: the request is accepted and the
            hard delete runs asynchronously (all related files are deleted, then
            the connector is removed from the database).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Connector'
        '400':
          description: Invalid request (e.g. malformed connector_id).
        '401':
          description: Unauthorized - Invalid or missing API key.
        '404':
          description: >-
            No connector found with this ID, or the user does not have
            permission to delete it.
components:
  schemas:
    Connector:
      type: object
      description: >-
        An ingestion source (e.g. email inbox or investment research / broker
        feed). Returned by Create/Get/Update connector and List connectors.
      properties:
        connector_id:
          type: string
          format: uuid
          description: >-
            Unique identifier for the connector. Use when updating, deleting, or
            filtering documents by connector.
          example: 019a9612-bfad-758c-884e-37dd8c6ad2cb
        user_id:
          type: string
          description: ID of the user who owns the connector.
          example: user_id_001
        org_id:
          type: string
          description: ID of the organization the connector belongs to.
          example: org_id_001
        share_with_org:
          type: boolean
          description: >-
            If true, all members of your organization can access the processed
            content. If false, only you can access the processed content.
          example: true
        label:
          type: string
          description: Display name for the connector (e.g. for UI or admin lists).
          example: Broker Research - Daily Reports
        type:
          type: string
          description: >-
            Connector type. Determines the configuration and how content is
            ingested.
          enum:
            - email
            - investment_research
        description:
          type: string
          description: >-
            Optional human-readable description of what the connector is used
            for.
          example: Collects daily reports from the broker's research team
        config:
          description: >-
            Type-specific settings. Email connectors return inbox and allowed
            senders; investment research connectors return `user_id` only (never
            `user_password`).
          nullable: true
          oneOf:
            - $ref: '#/components/schemas/EmailConnectorResponseConfig'
              title: Email
            - $ref: '#/components/schemas/InvestmentResearchConnectorResponseConfig'
              title: Investment research
        files_count:
          type: integer
          description: >-
            Number of files ingested through this connector, when tracked (e.g.
            investment research sync).
          example: 10
        last_sync_at:
          type: string
          format: date-time
          nullable: true
          description: >-
            Timestamp of the last sync from the external source, when
            applicable.
          example: '2026-04-07T09:36:34.195040Z'
        last_sync_status:
          type: string
          nullable: true
          description: Outcome of the last sync (e.g. SUCCESS), when applicable.
          example: SUCCESS
        last_sync_error_msg:
          type: string
          nullable: true
          description: Error message from the last sync when it failed; null on success.
          example: null
        last_sync_count:
          type: integer
          nullable: true
          description: Number of items processed in the last sync, when applicable.
          example: 3200
        created_at:
          type: string
          format: date-time
          description: Timestamp when the connector was created.
          example: '2026-02-11T11:01:09.574095Z'
        updated_at:
          type: string
          format: date-time
          description: Timestamp when the connector was last updated.
          example: '2026-02-11T11:01:09.574102Z'
        archived:
          type: boolean
          description: Whether the connector is archived.
          example: false
      required:
        - connector_id
        - user_id
        - org_id
        - share_with_org
        - label
        - type
        - created_at
        - updated_at
        - archived
    EmailConnectorResponseConfig:
      type: object
      description: >-
        Email connector configuration as returned by the API. Contains
        allowed_emails and the inbox email address.
      properties:
        allowed_emails:
          type: array
          description: Sender addresses that are allowed to send content to this connector.
          items:
            type: string
            format: email
          example:
            - user@example.com
            - admin@example.com
        email_hash:
          type: string
          description: Unique hash identifier for the email connector.
          example: a1b2c3d4e5f6
        email:
          type: string
          format: email
          description: >-
            Inbox address to forward emails to; only messages from
            allowed_emails are processed.
          nullable: true
          example: connector@bigdata.com
    InvestmentResearchConnectorResponseConfig:
      type: object
      description: >-
        Investment research connector configuration as returned by the API. Only
        non-secret fields are present.
      properties:
        user_id:
          type: string
          description: Broker or research portal user id (often an email address).
          example: API@ravenpack.com
      required:
        - user_id
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY
      description: >-
        Your API key. Include it in every request as the X-API-KEY header.
        Create and manage keys in the Developer Platform.

````