Account and API keys

• Email: create an account with your work email and confirm it with the 6-digit code we send. Each password sign-in also asks for a short one-time code sent to your inbox.
• Google: use the Google button on sign in or sign up. Nothing to set up on your side.

1. Open Dashboard → API keys.
2. Give the key a name that says where it runs (Production backend, Make), then click Create key.
3. Copy it at once: it is shown only this one time. Store it in your server’s environment, Make connection or n8n credential.

A key has full access to your workspace: it can schedule, list, read and cancel every job. Keys are not limited to one action or one integration. Never put a key in a browser, a mobile app or a public page. If one leaks, revoke it in the list under Your keys and create a new one.

On Free, creating a second key is refused (API_KEY_LIMIT_EXCEEDED) until you revoke the first one or upgrade.

Keys start with wh_live_, or wh_test_ when you check Test key. A test key is a label for your own bookkeeping, not a sandbox: its webhooks are delivered for real and count toward your monthly quota, like a live key’s.

The one difference: with a test key, a webhook to the built-in test receiver (https://webhookscheduler.com/api/demo/receiver) may have a runAt up to 5 minutes in the past, and then runs one second later. The ready-made test commands rely on it. Everywhere else, runAt must be in the future.

Send it in the Authorization header of every API call:

The older x-api-key: wh_live_YOUR_KEY header still works for existing integrations. Every endpoint is in the API reference.