Conduyt Drip Tracks API

The Drip Tracks API from Conduyt — 3 operation(s) for drip tracks.

Operations 6

DELETE /drip-tracks/{id} Delete drip-tracks id #
GET /drip-tracks/{id} Get drip-tracks id #
PATCH /drip-tracks/{id} Update drip-tracks id #
POST /drip-tracks/import-steps Create / invoke drip-tracks import-steps #
GET /drip-tracks List drip-tracks #
POST /drip-tracks Create / invoke drip-tracks #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/conduyt-com:conduyt-com-drip-tracks-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

conduyt-com-drip-tracks-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Conduyt Drip Tracks 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: Drip Tracks
paths:
  /drip-tracks/{id}:
    delete:
      x-generated: true
      operationId: deleteDripTracksId
      summary: Delete drip-tracks id
      tags:
      - Drip Tracks
      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
      responses:
        '204':
          description: Deleted
    get:
      x-generated: true
      operationId: getDripTracksId
      summary: Get drip-tracks id
      tags:
      - Drip Tracks
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataEnvelope'
    patch:
      x-generated: true
      operationId: patchDripTracksId
      summary: Update drip-tracks id
      tags:
      - Drip Tracks
      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: true
        content:
          application/json:
            schema:
              type: object
              properties:
                channel:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                complianceProfile:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                exitConditions:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                isActive:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                label:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                name:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                reEntryAllowed:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                steps:
                  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'
  /drip-tracks/import-steps:
    post:
      x-generated: true
      operationId: postDripTracksImportSteps
      summary: Create / invoke drip-tracks import-steps
      tags:
      - Drip Tracks
      parameters:
      - 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: true
        content:
          application/json:
            schema:
              type: object
              required:
              - items
              properties:
                items:
                  maxItems: 200
                  type: array
                  items:
                    type: object
                    properties:
                      trackName:
                        type: string
                        pattern: ^[a-z0-9][a-z0-9_]{0,79}$
                      steps:
                        maxItems: 250
                        type: array
                        items:
                          type: object
                          properties:
                            dayOffset:
                              type: integer
                              minimum: 0
                              maximum: 9007199254740991
                            timeWindow:
                              anyOf:
                              - type: string
                                maxLength: 50
                              - type: 'null'
                            channel:
                              type: string
                              enum:
                              - sms
                              - email
                              - both
                            templateId:
                              anyOf:
                              - type: string
                                maxLength: 200
                              - type: 'null'
                            templateBody:
                              anyOf:
                              - type: string
                                maxLength: 10000
                              - type: 'null'
                            mergeTags:
                              default: []
                              maxItems: 100
                              type: array
                              items:
                                type: string
                                pattern: ^\$\[[A-Za-z0-9_.-]+\]$
                          required:
                          - dayOffset
                          - channel
                    required:
                    - trackName
                    - steps
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                type: object
                properties:
                  data:
                    type: object
                    properties:
                      updated: {}
                      errors: {}
                    required:
                    - updated
                    - errors
                required:
                - data
  /drip-tracks:
    get:
      x-generated: true
      operationId: getDripTracks
      summary: List drip-tracks
      tags:
      - Drip Tracks
      responses:
        '200':
          description: Success
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DataEnvelope'
    post:
      x-generated: true
      operationId: postDripTracks
      summary: Create / invoke drip-tracks
      tags:
      - Drip Tracks
      parameters:
      - 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: true
        content:
          application/json:
            schema:
              type: object
              properties:
                channel:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                complianceProfile:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                exitConditions:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                isActive:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                label:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                name:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                reEntryAllowed:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
                steps:
                  description: Read by the handler from the JSON body (the route declares no schema for its type).
      responses:
        '201':
          description: Created
          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