Install Jentic One Beta

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.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdrips.com%2Fdrips" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fdrips.com%2Fdrips" | 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.

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

Insert a phone number into the disqualified register so Drips stops outreach

GET STARTED

Start building with Drips API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Drips 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

GET

/Disqualified/ExportRecords/{apiKey}

Export disqualified records

GET

/Reports/ScheduledCalls/{apiKey}

Export scheduled calls report

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Drips API by hand means handling its API-key auth, which travels both in the X-API-Key header and inside the operation path, and building each record action yourself. Through Jentic you install once, import Drips from the API Directory, store the key once, and your agent calls it.

Permission scoping

Drips actions target a record through the request body, so you limit the agent to the operations it needs, such as inserting a record or exporting disqualified records. You choose which operations are allowed, so state-changing calls like marking a record converted or disqualified are not included unless you add them.

Credential isolation

Your Drips API key is stored once, encrypted, by your own Jentic One instance and injected into the X-API-Key header and operation path at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'insert a Drips record' or 'export disqualified records', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without reading the docs.

FAQs

Specific to using Drips 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 with Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Drips API?

Yes. Because you run Jentic One yourself, you decide which Drips operations your agent may call, so you can allow a read-and-load agent only to insert records with POST /Record/Insert/{apiKey} or export the disqualified register with GET /Disqualified/ExportRecords/{apiKey}. State-changing calls, such as marking a record converted with POST /Record/Converted/{apiKey} or adding a number to the disqualified list with POST /Disqualified/Insert/{apiKey}, stay unavailable unless you explicitly add them. Your own rules also control which stored credentials the agent may use, keeping the Drips API key scoped to the operations you permit.

Drips API

Name: Drips API
Brand: Drips API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticCommunicationsSms MessagingapiKey7 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to insert a new lead into a Drips outreach campaign, Mark a Drips record as converted after a sale closes, Add a phone number to the Drips disqualified list, Export the list of Drips disqualified numbers for compliance

Not supported: Does not handle email campaigns, voice calls, or CRM pipeline management - use for SMS-focused conversational outreach record management within Drips only.

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.

Jentic One on Github View OpenAPI Document

Connect the Drips API to your agent

Capabilities

Start building with Drips API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Drips API