DOCS · GETTING STARTED
Getting Started
Create a Recurrence Cloud account, set up your first app, and fire your first signed schedule — in about five minutes.
This walkthrough takes you from zero to a working, signed schedule — the account, the app, and the one API call that makes something happen on a schedule. About five minutes, one terminal.
1. Create your account
Sign up at app.recurrence.cloud/signup — the 30-day Pro trial needs no credit card. After sign-in you land in the dashboard with a fresh organization.
2. Create an app
In the dashboard: Apps → New App. An app is the unit that owns everything you’ll schedule — webhooks, schedules, events, and API keys — and it carries a secret that signs your deliveries.
curl -X POST https://api.recurrence.cloud/api/apps \
-H "Content-Type: application/json" \
-d '{ "name": "my-first-app", "organizationId": "<org id>" }'
3. Generate an API key
Still in Apps, create an API key for the app. The raw key is shown once — store it. This key both calls the programmatic API (X-API-Key) and identifies your tenant on every request.
curl -X POST https://api.recurrence.cloud/api/api-keys \
-H "Content-Type: application/json" \
-d '{ "name": "local-dev", "appId": "<app id>" }'
{
"id": "…",
"keyPrefix": "rc_1a2b",
"rawKey": "the-only-time-you-see-this"
}
4. Register a webhook
A webhook is where scheduled deliveries go — any HTTPS endpoint you control. A public webhook.site URL is perfect for a first look.
curl -X POST https://api.recurrence.cloud/api/v1/webhooks \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "https://webhook.site/your-uuid", "appId": "<app id>" }'
5. Light the fuse
Create a schedule, the webhook, and the event in one call — fire in about a minute from now:
curl -X POST https://api.recurrence.cloud/api/v1/schedules/with-webhook \
-H "X-API-Key: $API_KEY" \
-H "Content-Type: application/json" \
-d '{
"schedule": { "name": "first-fire", "frequency": "minute", "interval": 1, "timezone": "UTC" },
"webhook": { "url": "https://webhook.site/your-uuid", "secret": "<a long random string>" },
"event": { "subject": "hello-rc", "payload": { "type": "demo.ping" } },
"appId": "<app id>"
}'
You’ll get 201 with the schedule id and, roughly sixty seconds later, your webhook endpoint receives a POST carrying:
{
"batchId": "bat_…",
"events": [ { "subject": "hello-rc", "data": { "type": "demo.ping" } } ],
"attempt": 1,
"firedAt": "2026-01-01T12:00:00.500Z"
}
⚠ That delivery is signed. In production, your receiver must verify the
X-Webhook-Signatureheader — that’s the next walkthrough.
6. Watch it in the activity trail
Open Activity in the dashboard (or GET /api/activity) — every delivery is recorded with its status code, latency, and attempt number. This trail is your primary debugging surface; walkthrough 6 covers it in depth.
Clean up
Delete the demo schedule via the dashboard (Schedules → ⋯ → Delete) or:
curl -X DELETE https://api.recurrence.cloud/api/schedules/<schedule id> \
-H "X-API-Key: $API_KEY"
Next: Authentication — the three auth modes and when to use each.