Drip API

Name: Drip API
Brand: Drip API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingMarketing Automationbasic, bearer44 EndpointsREST

For Agents

Manage Drip subscribers, send broadcasts, trigger workflows, and record shopper events for e-commerce email automation.

Connect the Drip API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Drip 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 Drip API.

Create or update subscribers in bulk through /v2/{account_id}/subscribers/batches with up to 1000 records per call

Apply and remove tags on subscribers to drive segmented campaign sends

Record custom shopper events such as cart abandonment to start workflow triggers

Activate, pause, or list campaign subscribers to control automated email sequences

GET STARTED

Start building with Drip API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Drip API, keeping it validated and agent-ready. Drip is an e-commerce CRM and email marketing platform that lets agents manage subscribers, send broadcasts, run multi-step workflows, and trigger campaigns based on customer events. The v2 REST API exposes 44 endpoints covering subscribers, tags, custom fields, broadcasts, workflows, conversions, and shopper activity such as carts and orders. Authentication supports both HTTP Basic with an API token and Bearer OAuth2 access tokens, scoped to a Drip account ID that prefixes most resource paths.

Use Cases

Patterns agents use Drip API for, with concrete tasks.

★ E-Commerce Lifecycle Email Automation

Sync shopper behaviour from a Shopify or custom storefront into Drip so that workflows fire on cart abandonment, order placed, and post-purchase events. Agents post events to /v2/{account_id}/events and orders to the orders endpoints, then activate campaigns to nurture buyers. Implementation typically takes a day with the batch event endpoint instead of synchronous per-event calls.

Post a cart_abandoned event for subscriber email shopper@example.com with cart total $129 to /v2/{account_id}/events and confirm a 204 response.

Subscriber List Hygiene and Tagging

Maintain clean, well-segmented subscriber lists by batch updating profiles, applying tags based on engagement, and unsubscribing inactive contacts. Drip exposes /v2/{account_id}/subscribers/batches and /v2/{account_id}/unsubscribes/batches for bulk hygiene operations. Agents can run weekly cleanup jobs that previously required manual CSV imports.

Submit a batch of 500 subscribers with the tag VIP-2026 to /v2/{account_id}/subscribers/batches and verify each record returns a 201 status.

Campaign Performance Reporting

Pull campaign-level metrics by listing campaigns and their subscribers, then mapping them to internal analytics tables. Drip exposes campaign listings, individual campaign fetches, and subscriber rosters per campaign so dashboards can surface signups, opens, and conversions. Useful for marketing ops teams replacing manual CSV exports.

Call GET /v2/{account_id}/campaigns followed by GET /v2/{account_id}/campaigns/{campaign_id}/subscribers for each active campaign and aggregate counts.

AI Agent E-Commerce Concierge

An AI agent integrated via Jentic discovers Drip operations by natural-language search, loads operation schemas, and fires lifecycle events on behalf of a merchant. The agent registers new subscribers, tags them by source, posts purchase events, and starts a welcome workflow without the developer hand-coding the auth or pagination loop. Time-to-first-call drops from days of OAuth wiring to under an hour.

Search Jentic for 'create a Drip subscriber', load the schema, then create subscriber email=newuser@example.com with tag source-ai-agent in account 1234567.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/v2/{account_id}/subscribers

Create or update a subscriber

POST

/v2/{account_id}/subscribers/batches

Batch create or update up to 1000 subscribers

POST

/v2/{account_id}/events

Record a custom event for workflow triggers

POST

/v2/{account_id}/tags

Apply a tag to a subscriber

GET

/v2/{account_id}/campaigns

List all campaigns

POST

/v2/{account_id}/campaigns/{campaign_id}/activate

Activate a campaign

POST

/v2/{account_id}/subscribers

Create or update a subscriber

POST

/v2/{account_id}/subscribers/batches

Batch create or update up to 1000 subscribers

POST

/v2/{account_id}/events

Record a custom event for workflow triggers

POST

/v2/{account_id}/tags

Apply a tag to a subscriber

GET

/v2/{account_id}/campaigns

List all campaigns

Why Jentic?

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

Credential isolation

Drip API tokens or OAuth bearer tokens are stored encrypted in the Jentic vault. Agents receive a scoped execution token at call time; raw Drip credentials never enter the agent's prompt or memory.

Intent-based discovery

Agents search Jentic with intents like 'add a Drip subscriber' or 'send a Drip broadcast' and receive the matching operation plus its input schema, removing the need to browse Drip's developer docs.

Time to first call

Direct Drip integration: 1-3 days for OAuth, account scoping, batch payload shaping, and webhook signature validation. Through Jentic: under 1 hour using search, load, execute.

FAQs

Specific to using Drip API through Jentic.

Why is there no official OpenAPI spec for Drip API?

Drip does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Drip 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 Drip API use?

The Drip API supports HTTP Basic authentication with an API token (used as the username) or OAuth2 Bearer access tokens. Through Jentic, the credential is stored in the encrypted vault and injected at execution time so the API token never enters the agent context.

Can I trigger a workflow for a subscriber with the Drip API?

Yes. List workflows under /v2/{account_id}/workflows, then start one for a subscriber using the workflow trigger endpoint. Most agent flows combine a POST to /v2/{account_id}/subscribers to create or update the contact with a workflow start call.

What are the rate limits for the Drip API?

Drip enforces a rate limit of approximately 3600 requests per hour per account. The OpenAPI spec does not encode the exact value, so check the X-RateLimit response headers on each call and back off when the remaining count approaches zero.

How do I record a shopper event with the Drip API through Jentic?

Search Jentic for 'record a Drip event', load the schema for POST /v2/{account_id}/events, then execute with the email, action name, and properties. Jentic resolves the account_id from your stored credential so the agent only supplies the event payload.

Does the Drip API support batch operations?

Yes. The /v2/{account_id}/subscribers/batches, /v2/{account_id}/unsubscribes/batches, and /v2/{account_id}/events/batches endpoints accept up to 1000 records per request, which is the recommended path for bulk imports and migrations.

Drip API

Connect the Drip API to your agent

Capabilities

Start building with Drip API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs