Drips API

Name: Drips API API
Brand: Drips API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCommunicationsSms MessagingapiKey7 EndpointsREST

For Agents

Insert leads, mark conversion or disqualification, and export Drips reports so an agent can drive conversational outreach lifecycle from external systems.

Connect the Drips API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Drips API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Drips API API.

Insert a new outreach record into Drips with contact and campaign metadata

Mark a Drips record as closed when the contact lifecycle ends

Mark a Drips record as converted when the lead becomes an opportunity

Update the disposition on an existing Drips record

GET STARTED

Start building with Drips API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Drips API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Drips API, keeping it validated and agent-ready. Drips is a conversational outreach platform that combines AI-driven texting with human handoff for sales, lead nurture, and re-engagement campaigns. The API exposes record ingestion (insert, close, convert, dispositioned), disqualified number management, and report exports for scheduled calls. Authentication is via an X-API-Key header in addition to a path-based key, suitable for batch ingestion of CRM records into Drips outreach campaigns.

Use Cases

Patterns agents use Drips API API for, with concrete tasks.

★ CRM-to-Drips Lead Loading

Push qualified leads from the CRM into Drips outreach campaigns so the platform can begin conversational follow-up. The agent calls POST /Record/Insert/{apiKey} with each new lead's contact details and campaign assignment, ensuring outreach starts within minutes of the lead landing in the CRM. This replaces manual CSV uploads and shortens speed-to-first-touch.

POST /Record/Insert/{apiKey} for each new CRM lead with name, phone, and target campaign id.

Conversion and Closure Tracking

Reflect downstream lead outcomes back into Drips so reporting on outreach impact is accurate. The agent calls POST /Record/Converted/{apiKey} when a lead becomes a customer and POST /Record/Closed/{apiKey} when the contact reaches a final state, keeping Drips's view of conversion in sync with the CRM source of truth.

On a CRM stage change to 'Closed Won', POST /Record/Converted/{apiKey} with the corresponding Drips record id.

Disqualification and Compliance Hygiene

Manage opt-outs and compliance flags by inserting numbers into the Drips disqualified register and exporting the full list for audit. The agent calls POST /Disqualified/Insert/{apiKey} when a customer opts out via another channel, then runs scheduled exports through GET /Disqualified/ExportRecords/{apiKey} to validate the register against the master suppression list.

POST /Disqualified/Insert/{apiKey} for each new opt-out, then nightly export the full disqualified list via GET /Disqualified/ExportRecords/{apiKey}.

AI Agent Outreach Operations

Through Jentic, an AI agent can take 'load these 50 leads into the Q3 nurture campaign' and resolve it to the Drips Record/Insert operation without browsing docs. Jentic injects the API key from the vault and validates the input payload schema. End-to-end setup is under an hour from sign-up.

Use Jentic search for 'insert a Drips record', load the POST /Record/Insert/{apiKey} operation, and execute it for a batch of 50 leads with campaign id 'q3-nurture'.

Key Endpoints

7 endpoints — jentic publishes the only available openapi specification for drips api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/Record/Insert/{apiKey}

Insert a new record

POST

/Record/Closed/{apiKey}

Mark a record as closed

POST

/Record/Converted/{apiKey}

Mark a record as converted

POST

/Record/Disposition/{apiKey}

Update record disposition

POST

/Disqualified/Insert/{apiKey}

Add a disqualified record

GET

/Disqualified/ExportRecords/{apiKey}

Export disqualified records

GET

/Reports/ScheduledCalls/{apiKey}

Export scheduled calls report

POST

/Record/Insert/{apiKey}

Insert a new record

POST

/Record/Closed/{apiKey}

Mark a record as closed

POST

/Record/Converted/{apiKey}

Mark a record as converted

POST

/Record/Disposition/{apiKey}

Update record disposition

POST

/Disqualified/Insert/{apiKey}

Add a disqualified record

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Drips API keys are stored encrypted in the Jentic vault and injected as the X-API-Key header (and into the operation path) at execution time. Agents receive a scoped reference, never the raw key.

Intent-based discovery

Agents search by intent (e.g. 'insert a Drips record') and Jentic returns the POST /Record/Insert/{apiKey} operation with its input schema, so the agent calls the right endpoint without reading docs.

Time to first call

Direct Drips integration: 1 day for auth, record insert plumbing, and disqualification handling. Through Jentic: under 30 minutes from sign-up to first record loaded.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Twilio API

Twilio is the underlying messaging fabric for many SMS use cases; Drips layers conversational outreach orchestration on top.

Choose Twilio when you need raw SMS send and receive infrastructure. Choose Drips when conversational AI plus human handoff is the goal.

Alternative

Salesloft API

Salesloft drives email-and-call outbound cadences; Drips focuses on conversational SMS and AI-led nurture.

Choose Salesloft when SDRs run multi-channel cadences. Choose Drips when SMS conversation is the primary motion.

Complementary

HubSpot Marketing API

HubSpot is the CRM source of truth; Drips runs the conversational outreach against the contacts HubSpot owns.

Use HubSpot to maintain contact and lifecycle data. Use Drips to run conversational outreach on top of that data.

FAQs

Specific to using Drips API API through Jentic.

Why is there no official OpenAPI spec for Drips API?

Drips does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Drips API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Drips API use?

Drips uses an API key passed as the X-API-Key header (and embedded in the path on each operation). Through Jentic, that key is stored encrypted in the vault and injected at execution time, so it never enters the agent's context.

Can I add a number to the Drips disqualified list?

Yes. POST /Disqualified/Insert/{apiKey} adds a phone number to the disqualified register so Drips stops outreach to it. Use GET /Disqualified/ExportRecords/{apiKey} to export the current register for audit.

How do I insert a lead into a Drips campaign through Jentic?

Run pip install jentic, search for 'insert a Drips record', load the POST /Record/Insert/{apiKey} operation, and execute it with the lead's contact details and campaign id. Jentic returns the input schema so the agent assembles a valid payload without reading docs.

Can I report conversions back to Drips?

Yes. POST /Record/Converted/{apiKey} marks a record as converted, and POST /Record/Closed/{apiKey} closes a record at the end of its lifecycle. Use POST /Record/Disposition/{apiKey} for finer-grained outcome tagging.

What are the rate limits for the Drips API?

The published spec does not declare explicit per-endpoint limits. Implement client-side throttling for batch loads and treat 429 responses as the signal to slow down. For high-volume ingestion, confirm thresholds with Drips directly.