Conduyt Emails API

openapi: 3.2.0
info:
  title: Conduyt Emails 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: Emails
paths:
  /emails/health:
    get:
      x-generated: true
      operationId: getEmailsHealth
      summary: List emails health
      tags:
      - Emails
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      domain: {}
                      windowDays:
                        type: number
                      metrics: {}
                      checks: {}
                      recentFailures: {}
                    required:
                    - domain
                    - windowDays
                    - metrics
                    - checks
                    - recentFailures
                required:
                - data
  /emails/sequences/{id}/preflight:
    post:
      x-generated: true
      operationId: postEmailsSequencesIdPreflight
      summary: Create / invoke emails sequences id preflight
      tags:
      - Emails
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      - name: dry_run
        in: query
        required: false
        description: Validate the mutation without persisting changes.
        schema:
          type: boolean
      - name: sandbox
        in: query
        required: false
        description: Run the mutation in sandbox mode.
        schema:
          type: boolean
      requestBody:
        required: false
        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).
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      sequenceId: {}
                      total: {}
                      eligible: {}
                      skipped: {}
                      errors: {}
                      warnings: {}
                      missingTemplates: {}
                      domainReady: {}
                      contacts:
                        type: array
                    required:
                    - sequenceId
                    - total
                    - eligible
                    - skipped
                    - errors
                    - warnings
                    - missingTemplates
                    - domainReady
                    - contacts
                required:
                - data
  /emails/templates/{id}/usage:
    get:
      x-generated: true
      operationId: getEmailsTemplatesIdUsage
      summary: Get emails templates id usage
      tags:
      - Emails
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      templateId: {}
                      count: {}
                      uses: {}
                    required:
                    - templateId
                    - count
                    - uses
                required:
                - data
  /emails/sequences/{id}/pick-from-list:
    post:
      x-generated: true
      operationId: postEmailsSequencesIdPickFromList
      summary: Create / invoke emails sequences id pick-from-list
      tags:
      - Emails
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      - name: dry_run
        in: query
        required: false
        description: Validate the mutation without persisting changes.
        schema:
          type: boolean
      - name: sandbox
        in: query
        required: false
        description: Run the mutation in sandbox mode.
        schema:
          type: boolean
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                cursor:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                limit:
                  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).
                smartViewId:
                  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:
                      sequenceId: {}
                      listTotal: {}
                      scanned: {}
                      alreadyIn: {}
                      contacts: {}
                      ineligible: {}
                      blockers:
                        type: array
                      cursor: {}
                      exhausted: {}
                    required:
                    - sequenceId
                    - listTotal
                    - scanned
                    - alreadyIn
                    - contacts
                    - ineligible
                    - blockers
                    - cursor
                    - exhausted
                required:
                - data
  /emails/sequences/senders:
    get:
      x-generated: true
      operationId: getEmailsSequencesSenders
      summary: List emails sequences senders
      tags:
      - Emails
      parameters:
      - name: channel
        in: query
        required: false
        description: Query parameter read by this route.
        schema:
          type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataEnvelope'
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