Skip to main content

Waitlist API

Collect signups before launch and turn them into users afterwards. Each signup gets a referral code, invites go out in first-come order, and the whole list exports as CSV.

Get an API key → Waitlist in Next.js

What exists today

  • Signups arrive through a hosted page, an iframe embed, a script-tag widget or a direct API call from your own form.
  • Each signup carries a referral code. Referred signups are attributed to the referrer and ranked on a public leaderboard.
  • Batch invites email the next N people in line with a link to a welcome page or a URL you configure. A daily send cap prevents accidental floods.
  • Bot protection uses Cloudflare Turnstile on the hosted page; the API rate-limits per key and per IP.
  • GDPR: signups can be hard-deleted by token, and exports are signed URLs that expire.
  • Each signup records where it came from: the referring site's hostname, UTM source, medium and campaign, and the page the form was on. The hosted page and the script widget collect this without cookies or browser storage.
  • An existing list can be imported from CSV in the dashboard or through the API. Bad rows are skipped and counted, never fatal, and nobody is emailed by an import.
  • On Builder, the signup receipt and the invite email can be rewritten in your own words. The unsubscribe footer is always added by Launch.

Endpoints

POST /v1/waitlist/signups Add an email (publishable key allowed)
GET /v1/waitlist/signups List signups
GET /v1/waitlist/stats Aggregate counts
GET /v1/waitlist/leaderboard Top referrers
POST /v1/waitlist/invites Invite the next N or a specific email
PATCH /v1/waitlist/settings Pause intake, custom copy, welcome URL
GET /v1/waitlist/export Signed CSV download URL
POST /v1/waitlist/import Import up to 1,000 existing signups per call
PUT /v1/waitlist/email-templates/{kind} Your own copy for the receipt or invite email (Builder)

Full reference with request and response schemas: docs.nordva.dev. Every response uses the same envelope and stable error codes.

MCP tools

The same operations are available to Claude Code, Claude Desktop and Cursor through the Nordva MCP server at mcp.nordva.dev:

  • add_to_waitlist
  • import_waitlist
  • get_waitlist_stats
  • get_waitlist_leaderboard
  • invite_from_waitlist
  • export_waitlist
  • update_waitlist_settings
  • get_waitlist_embed_snippet

Arguments, example prompts and client setup →

Questions

Is double opt-in supported?
On paid plans a confirmation email is sent and the signup records its confirmation time. Unconfirmed addresses can be resent a confirmation once every five minutes.
How are referrals credited?
The referral code from the ?ref= parameter is stored on the new signup. Self-referrals and obviously automated patterns are flagged rather than credited.
Can I embed the form on my own site?
Yes, either as an iframe of the hosted page or with the script-tag widget served from cdn.nordva.dev. Both post to the same endpoint.