For Developers

API reference, webhook integration, and automation guides for building on the Warpflow Signals platform.

Build on Warpflow Signals

Warpflow Signals exposes a REST API for sending events, retrieving conversations, managing email, and triggering AI-powered actions. Whether you're connecting Zapier, building a custom CRM integration, or sending email programmatically — start here.

Base URL

https://api.warpflow.ai/api/v1/

Authentication

Every API request requires a Bearer token in the Authorization header:

Authorization: Bearer <your_api_key>

Create API keys in the Signals dashboard under Settings → API Keys. Keys are tenant-scoped, audited, and support rotation with a 72-hour grace period. See the authentication guide for full details.

Quick links

I want to...	Go here
Authenticate API requests	Authentication
Send events from any platform	Webhooks
Send and receive email via API	Email API
Use AI actions in Zapier / Make / n8n	Zapier Integration
See common integration patterns	Integration Recipes
Browse all endpoints	API Reference
Understand error responses	Errors

Quick test

Verify your API key works with a simple request:

curl -s -H "Authorization: Bearer YOUR_API_KEY" \
  https://api.warpflow.ai/api/v1/tenants/YOUR_TENANT_ID/conversations \
  | head -c 200

A successful response returns a JSON object with a conversations array. If you get a 401, check that your API key is active in the dashboard.

How the API is organized

Webhooks — Send inbound events (form submissions, CRM updates, messages) into the Signals pipeline for classification, scoring, and routing.

AI Actions — Call individual pipeline steps directly: classify a conversation, score a contact, or generate a brand-voice reply. These are the same actions available in Zapier.

Email — Send email through connected accounts, manage aliases and signatures, and view email conversations with full thread context.

Conversations — Retrieve multi-channel conversation history (SMS, email, voice) grouped by contact.

Config — Read and update tenant configuration (routing rules, templates, brand voice, etc.) programmatically.