Webhooks and API

Send new signups to the tools you use.

Build your own form with the API, or send Standard signup and Preorder events to your automation service. Connect a destination once instead of exporting each morning.

Works with: API contracts vary by workflow. Webhooks cover Standard and Preorders only.

Create your formOpen the developer reference

Example · Standard signup to your destination

Customer joins your Standard list

Accepted signup with available owner details

Signed webhook · Starter / Pro

Event excerpt · sample data

{
  "event": "entry.created",
  "entry": {
    "position": 12,
    "email": "[email protected]"
  }
}
Your automation maps the fields

Your spreadsheet, CRM, or database

For example: append a row for Alex’s signup.

The receiving automation needs its own setup. This illustrates a webhook connection, not a native integration. Queue and Booking webhook events are not supported.

How to use it

Plan availability: The public API and server-side API keys are available on all plans. Webhooks for Standard and Preorders require Starter or Pro.

  1. Choose the workflow endpoint

    GET /api/v1/forms/{formId} for the public definition. Submit signups to /signups, queue tickets to /tickets, preorders to /orders, and bookings to /bookings under that form URL.

  2. Connect an event destination

    On Starter or Pro, set a webhook URL, save it to draft, and publish. Standard sends entry.created and entry.status_changed; Preorders send order.created and order.status_changed. Queue and Booking events are not part of this webhook contract.

  3. Verify the delivery

    Use the delivery log and a test event to check your receiver. Verify the signature, handle duplicate deliveries, and review failures. A receiving service such as Zapier or Make needs its own setup; this is a webhook connection.

Standard API example · run on your server

curl -X POST https://unwaited.com/api/v1/forms/YOUR_FORM_ID/signups \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $UNWAITED_API_KEY" \
  -d '{"email":"[email protected]"}'

Replace the page key and add any required fields from /form. API keys stay on your server. A fresh signup returns a private status link; show or save it for the customer.

Before you set it up

Can I fetch everyone who signed up?

There is no public endpoint that lists all Standard entries. Use the authenticated CSV export or receive supported events through webhooks. Queue has a separate private ticket-status endpoint at /tickets/{token}.

Do held Standard entries send webhooks?

No. Their side effects wait until release. Held customer details are also excluded from CSV exports.

How do I keep API keys and status links private?

Send a Bearer API key only from your server. Browser submissions use the captcha flow. Show or save a fresh customer status link when returned; repeat submissions do not disclose the private link again.

Related features

Choose the page that fits your work.

Free includes 300 signups per account each month. Choose a signup list, live queue, booking page, or preorder batch.

Create your form