Skip to main content
Email supports transactional sends, hub-specific sending configuration, templates, drip campaigns, suppressions, webhooks, and unsubscribe.

​
Configure hub sending

GET /v1/hubs/{hub_id}/email-config
PUT /v1/hubs/{hub_id}/email-config
POST /v1/hubs/{hub_id}/email-config/test

​
Create templates

POST /v1/hubs/{hub_id}/email-templates
GET  /v1/hubs/{hub_id}/email-templates
POST /v1/hubs/{hub_id}/email-templates/{template_id}/preview

​
Create a drip campaign

POST /v1/hubs/{hub_id}/drip-campaigns
POST /v1/hubs/{hub_id}/drip-campaigns/{campaign_id}/steps
POST /v1/hubs/{hub_id}/drip-campaigns/{campaign_id}/activate
Use drip campaigns for welcome sequences, content drip, cart recovery, post-purchase nurture, and reactivation.

​
Suppressions and unsubscribe

Suppression endpoints help prevent sends to blocked or unsubscribed addresses: 
GET  /v1/hubs/{hub_id}/email-suppressions
POST /v1/hubs/{hub_id}/email-suppressions
GET  /unsubscribe
POST /unsubscribe
Email routes currently remain under /v1/... instead of /api/v1/.... Treat the generated API reference as the exact path source for email until those routes are folded into the canonical API prefix.

​
Drip admin enrollment

Admin enrollment endpoints (POST /enroll, DELETE /exit, and list enrollments) are wired but the underlying campaign-authoring surface (create/update/delete campaigns and steps) is not yet built. Calling those unbuilt methods returns 404 with code drip_admin_surface_unavailable instead of a 500. Track the campaign-authoring surface under the email phase-B milestone.