Conduyt Bulk API

openapi: 3.2.0
info:
  title: Conduyt Bulk API
  version: 1.0.0
  description: 'The Conduyt CRM API provides programmatic access to your CRM data including

    contacts, companies, deals, pipelines, tasks, notes, automations, invoices,

    email sequences, and more.


    ## Authentication


    All authenticated endpoints require a Bearer token (API key) in the

    `Authorization` header:


    ```

    Authorization: Bearer cdy_

    ```


    API keys are generated in **Settings > API Keys** within the Conduyt

    dashboard. Keys use the `cdy_` prefix and are hashed with bcrypt on

    creation — the full key is shown exactly once at creation time.


    Session cookie authentication (`conduyt_session`) is also supported for

    browser-based clients but is not recommended for integrations.


    ## Rate Limiting


    API keys enforce a per-key rate limit. New keys default to 100 requests per

    minute and can be configured at creation time or with PATCH `/api-keys/{id}`.

    Some public and provider-facing endpoints also enforce stricter per-IP or

    per-account limits. When exceeded, the API returns `429 Too Many Requests`

    with a `Retry-After` header indicating seconds until the next allowed

    request.


    | Endpoint Group | Limit |

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

    | API keys | Default 100 / min per key |

    | Login/reset | 5 / min per IP |

    | Registration | 3 / hour per IP |

    | Contact/Deal create | 30 / min per IP |

    | Inbound messages | 120 / min per account/IP |


    ## Pagination


    List endpoints support cursor-based pagination via query parameters:


    - `page` — Page number (default: 1)

    - `per_page` — Items per page (default: 50, max: 200)

    - `limit` — Accepted as an alias of `per_page` on `GET /contacts`; if both are

    sent they must carry the same value.


    A page size above the maximum, a non-integer, a value below 1, or a

    pagination key repeated with different values is rejected with `400`

    (the message names the parameter and the rule); nothing is silently

    clamped or ignored.


    Responses include a `meta` object: `{ page, per_page, total }`.


    An operation that documents its own pagination rules follows those instead.

    `GET /sms-providers/options` pages with an opaque `cursor` and a `limit`

    that is capped at 50 rather than rejected; its responses carry

    `meta: { nextCursor, truncated }`.


    ## Response Format


    All successful responses wrap data in a `data` envelope:

    ```json

    { "data": { ... } }

    ```


    Error responses use:

    ```json

    { "error": "Human-readable error message" }

    ```


    ## Multi-Tenancy


    Conduyt is multi-tenant. All data is scoped to the authenticated user''s

    current account. API keys are bound to a specific account at creation time.


    ## Webhook Events


    Outbound webhooks fire on events including:

    `contact.created`, `contact.updated`, `contact.deleted`,

    `deal.created`, `deal.updated`, `deal.won`, `deal.lost`,

    `task.created`, `task.completed`, `note.created`,

    `appointment.created`, `appointment.updated`,

    `form.submitted`, `invoice.paid`


    Payloads are signed with HMAC-SHA256 using the webhook''s secret. Retry

    schedule: 1m, 5m, 30m, 2h, 12h, 72h (7 total attempts including the initial delivery).'
  contact:
    name: Conduyt Support
    url: https://conduyt.app
    email: support@conduyt.app
  license:
    name: Proprietary
    url: https://conduyt.app/terms
servers:
- url: https://conduyt.app/api/v1
  description: Production
security:
- BearerAuth: []
tags:
- name: Bulk
paths:
  /bulk/contacts/dnc:
    post:
      x-generated: true
      operationId: postBulkContactsDnc
      summary: Create / invoke bulk contacts dnc
      tags:
      - Bulk
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                action:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                contactIds:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                reason:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                tier:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      updated: {}
                    required:
                    - updated
                required:
                - data
  /bulk/contacts/untag:
    post:
      x-generated: true
      operationId: postBulkContactsUntag
      summary: Create / invoke bulk contacts untag
      tags:
      - Bulk
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                contactIds:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                tagId:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataEnvelope'
  /bulk/contacts/delete-matching:
    post:
      x-generated: true
      operationId: postBulkContactsDeleteMatching
      summary: Create / invoke bulk contacts delete-matching
      tags:
      - Bulk
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                filter:
                  type: object
                  additionalProperties: true
                  description: The contacts-list filter (the same filter keys GET /contacts reads, including the compact cf, as strings or arrays of strings). A blank plain string of a key other than email is ignored; an empty array, or an array with any blank entry, under any non-email key (and an empty array under email) is 400 invalid_filter naming the key. Every supplied key must match its exact grammar (UUIDs, enums, ISO dates with a valid range, digits-only positive min_score, a non-empty valid JSON array for filters, one value for single-valued keys) or the request is 400 invalid_filter naming the key; a smart_view, smartListId or filters payload that names an audience with no conditions, or contains a negative clause on a closed account domain (tags by literal case-insensitive name, pipeline, pipeline stage, assignee, deal status, master status, appointment status) whose referent does not exist, or a rule or group with an unknown property, or an optedOutSms / optedOutEmail value other than exactly true or false, or a contains / equals / is clause on a case-insensitively compared field (email, phone, company, city, state, country, jobTitle) or a search / company value holding the wildcard characters % or _, or a rule the ordinary rule validators refuse, is 400 invalid_filter (the legacy filterPayload of POST /batch-operations follows the same strict contract); two keys naming the same custom field (cf[tier] and cf[ tier ], or the compact cf) are 400; the contacts list itself stays lenient; at least one non-blank value is required.
                  properties:
                    assigned_to:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    cf:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    company:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    company_id:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    created_from:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    created_to:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    email:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    exclude_master_status:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    filters:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    import_id:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    master_status:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    min_score:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    reachability:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    search:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    smartListId:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    smart_view:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    source:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    tag:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    tags:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    updated_from:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                    updated_to:
                      description: Read by the handler from the JSON body (the route declares no schema for its type).
                expectedTotal:
                  type: integer
                  minimum: 1
                  description: The count the list showed for this filter; a different count is refused with 409 expected_total_mismatch and nothing is deleted.
                continuation:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                ids:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      matched: {}
                      deleted: {}
                      skipped: {}
                      keptWithAppointments: {}
                      remaining: {}
                      remainingIds: {}
                      continuation: {}
                      done: {}
                      busy: {}
                      followupsQueued: {}
                    required:
                    - matched
                    - deleted
                    - skipped
                    - keptWithAppointments
                    - remaining
                    - remainingIds
                    - continuation
                    - done
                    - busy
                    - followupsQueued
                required:
                - data
components:
  schemas:
    DataEnvelope:
      type: object
      properties:
        data:
          description: Response payload (shape varies by endpoint)
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      description: 'API key authentication. Generate keys in Settings > API Keys.

        Keys use the `cdy_` prefix.


        Example: `Authorization: Bearer cdy_a1b2c3d4e5f6...`

        '
x-mcp:
  transport:
  - stdio
  - http
  orchestration: code
  endpoint_tools: hidden