Drift API

Name: Drift API API
Brand: Drift API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCRMCustomer Supportoauth2, bearer37 EndpointsREST

For Agents

Drive Drift conversations, contacts, accounts, and meetings so an agent can respond, route, and enrich in-platform chat activity end to end.

Quickstart

Get started with Drift API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"reply to a Drift conversation"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Drift API API.

List, retrieve, and update conversations across the Drift inbox

Send messages and notes into a conversation, including attachments

Trigger Driftbot interactions or update an in-flight Driftbot message

Create or update contacts and read their attributes and timeline events

Manage accounts that group contacts under shared customer entities

GET STARTED

Start building with Drift API API

Explore with Jentic

View OpenAPI Document

Use for: I need to list recent Drift conversations for triage, Send a chat reply into a Drift conversation, Create a new Drift contact for an inbound lead, Trigger a Driftbot interaction in an existing conversation

Not supported: Does not handle email campaigns, payment processing, or full CRM pipeline management — use for Drift conversations, contacts, and accounts only.

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

Jentic publishes the only available OpenAPI specification for Drift API, keeping it validated and agent-ready. Drift is a conversational marketing platform that pairs live chat, chatbots, and meeting scheduling with a structured contact and account model. The API exposes conversations, messages, contacts, contact attributes and timeline, users, accounts, meetings, playbooks, and tags — letting external systems both react to and orchestrate Drift conversations. Authentication supports OAuth 2.0 and bearer tokens for app integrations and headless backends respectively.

Use Cases

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

★ Inbound Lead Capture and Enrichment

Capture inbound leads from Drift conversations and enrich the matching contact record with structured firmographic data. The agent watches GET /conversations for new chats, calls POST /contacts to create or update the contact, then writes additional attributes through the contact attributes endpoint. This keeps Drift's contact data clean for downstream MAP and CRM sync.

On a new Drift conversation, POST /contacts with the lead's email and name, then list contact attributes via GET /contacts/attributes and update them with firmographic data.

Live Conversation Response

Reply to a Drift conversation from an external system — for example, a custom inbox or an LLM-driven assistant. The agent calls POST /conversations/{conversationId}/messages with the reply body and PATCH /conversations/{conversationId} for state changes. Private notes via POST /conversations/{conversationId}/timeline/notes keep agent-only context out of customer view.

POST /conversations/12345/messages with a templated reply, then POST /conversations/12345/timeline/notes with an internal note for the assigned rep.

Driftbot Orchestration

Use Drift's bot capabilities to qualify leads in-conversation by triggering Driftbot interactions or updating in-flight bot messages. The agent calls POST /conversations/{conversationId}/driftbot/trigger to start a flow and PATCH /conversations/{conversationId}/driftbot to revise a bot prompt mid-conversation, all while staying inside the platform's conversational UX.

Trigger a Driftbot qualification flow on conversation 12345 via POST /conversations/12345/driftbot/trigger and follow up with a PATCH to update the bot message text.

Account-Based Conversation Routing

Tie Drift conversations to account records so SDR and AE teams see a unified view of inbound activity per target account. The agent uses POST /accounts to keep account state aligned with the CRM and pulls users via GET /users/list to drive routing rules. Tags applied via the tags endpoints make those conversations filterable in reporting.

Upsert the account 'Acme Corp' via POST /accounts, then on each Acme conversation list users via GET /users/list to assign the right SDR.

AI Agent Conversational Assistant

Through Jentic, an AI agent can take 'reply to that Drift chat with the standard pricing answer' and resolve it to the Drift message creation operation without browsing docs. Jentic injects the OAuth or bearer credential from the vault and validates the message payload schema. End-to-end setup is under an hour from sign-up.

Use Jentic search for 'reply to a Drift conversation', load the POST /conversations/{conversationId}/messages operation, and execute it for conversation 12345 with the reply body.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/conversations

List conversations

POST

/conversations/{conversationId}/messages

Create a message in a conversation

POST

/conversations/{conversationId}/driftbot/trigger

Trigger a Driftbot interaction

POST

/contacts

Create or update a contact

GET

/contacts/{contactId}/timeline

Get contact timeline events

POST

/accounts

Create an account

GET

/users/list

List Drift users

GET

/conversations

List conversations

POST

/conversations/{conversationId}/messages

Create a message in a conversation

POST

/conversations/{conversationId}/driftbot/trigger

Trigger a Driftbot interaction

POST

/contacts

Create or update a contact

GET

/contacts/{contactId}/timeline

Get contact timeline events

Why though Jentic?

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

Credential isolation

Drift OAuth client credentials and bearer tokens are stored encrypted in the Jentic vault and injected only at execution time. Agents receive scoped references, never the raw secret.

Intent-based discovery

Agents search by intent (e.g. 'reply to a Drift conversation' or 'create a Drift contact') and Jentic returns the matching operation with its input schema. The agent calls the right endpoint without traversing 37-operation docs.

Time to first call

Direct Drift integration: 1-2 days for OAuth flow, conversation pagination, and contact upsert logic. Through Jentic: under an hour from sign-up to first message sent or contact created.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Intercom API

Intercom is the closest peer for conversational support and marketing; Drift leans further into B2B account-based motion.

Choose Intercom for product-led support workflows. Choose Drift when ABM and sales-led conversations are the priority.

Complementary

HubSpot Marketing API

HubSpot owns long-lived marketing and CRM context; Drift handles the live conversation.

Use HubSpot for nurture and pipeline. Use Drift to engage on the website and feed those interactions back.

Complementary

Salesloft API

Salesloft drives outbound sales sequences; Drift converts inbound chat into the same pipeline.

Use Salesloft for outbound cadences. Use Drift when an inbound chat creates an opportunity that should join a Salesloft cadence.

FAQs

Specific to using Drift API API through Jentic.

Why is there no official OpenAPI spec for Drift API?

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

Drift supports OAuth 2.0 for app integrations and bearer tokens for backend usage. Through Jentic, those credentials live encrypted in the vault and are injected at execution time, so they never enter the agent's context.

Can I send messages into a Drift conversation?

Yes. POST /conversations/{conversationId}/messages adds a message to an existing conversation, while POST /conversations/{conversationId}/timeline/notes records a private note visible only to assigned reps.

How do I create a Drift contact through Jentic?

Run pip install jentic, search for 'create a Drift contact', load the POST /contacts operation, and execute it with the contact's email and name. Jentic returns the input schema so the agent builds a valid payload without reading docs.

Can I trigger Driftbot interactions from the API?

Yes. POST /conversations/{conversationId}/driftbot/trigger starts a Driftbot flow on a specific conversation, and PATCH /conversations/{conversationId}/driftbot updates an in-flight bot message.

What are the rate limits for the Drift API?

The published spec does not declare explicit per-endpoint limits. Implement client-side backoff and treat 429 responses as the signal to slow down. For app integrations operating across many tenants, confirm thresholds with Drift directly.