REST, SDK, MCP, webhooks, and your own email provider — same key, same response shapes, no separate account per surface.
A plain JSON API over HTTPS. No client library required — every operation is one request, and the response is the same shape the SDK and MCP server return.
Call it from anywhere@enlistdev/sdk wraps the REST API in typed methods — same operations, same response shapes, autocomplete on every field.
Typed, zero boilerplateConnect once and Claude Code, Cursor, or any MCP-capable agent can create waitlists and add signups directly — no route handler to write by hand.
Wired into your agentEnlist POSTs a signed JSON body to your endpoint for five event types — new signups, removals, and signup-email delivered/opened/clicked.
Know the moment it happensEnlist-managed sending needs zero configuration. Or connect your own Resend key and send on your own domain — Enlist still tracks delivery, opens, and clicks either way.
Bring your own key, or don’tSend events straight to the tools you already run. Connect one from the dashboard or over the API — same config either way, and delivery is logged per attempt.
Posts a Block Kit message to a Slack incoming webhook as events fire, so the channel is the notification.
Read the docsPosts an embed to a Discord webhook as events fire, for a channel that tracks the waitlist as it fills.
Read the docsCreates and updates a Loops contact as people join, so your email sequences run off the waitlist itself.
Read the docsCaptures a PostHog event as each signup lands, so the waitlist shows up in the funnels you already have.
Read the docsSubscribes people to Kit as they join, so the newsletter you already send is the waitlist email.
Read the docsVote on the roadmap, or send data anywhere with webhooks in the meantime.