Test mode
wc_test_ keys work on a separate copy of your data, send no real email, and are never counted toward your plan.
Every organization has two modes, live and test, each with its own events, RSVPs, series and webhook endpoints. The key you use picks the mode:
| Key prefix | Mode |
|---|---|
wc_live_ | Live: real guests, real email, counted toward your plan |
wc_test_ | Test: everything else |
What test mode guarantees
- Isolated data. A test key can never read or change live data, and the other way round. Asking a test key for a live event's ID answers
404, as if it did not exist. Every object carriesmodeso you can tell which side it came from. - No real email. Confirmations, reminders and waitlist emails are recorded as
skippedbut never sent, even to a real address. - Not metered. Test RSVPs never count toward your monthly RSVP limit and are never locked.
- Webhooks still fire, to the endpoints you registered in test mode, with
"mode": "test"in the envelope. They are signed and retried exactly like live ones. That is how you test your handler. - The dashboard has a switch. The mode toggle at the top of the dashboard shows test data, test keys and test webhook endpoints; nothing you do there touches live guests.
- Same API. Endpoints, fields, errors and rate limits behave exactly as in live mode, so moving to live is a key swap.
The sandbox
POST /v1/sandbox creates a throwaway test organization with a key and a sample event, without an account. It lasts 24 hours. The quickstart uses it.
Going live
- Create a live key in the dashboard.
- Create your real events (test events do not move over).
- Register your webhook endpoints again with the live key; each mode has its own endpoints and signing secrets.
- Swap
wc_test_forwc_live_in your server's environment.
The widget needs no key. It follows the event: a test event shows test data.