Quick Start
This guide walks you through creating your first scheduled HTTP request with Recuro.
1. Create an account
Sign up at app.recurohq.com and create your team. Your team is the workspace where all your crons, queues, and jobs live.
2. Get your API token
Go to Settings > API and generate a token. You’ll use this to authenticate all API requests.
3. Create a cron job
Use the dashboard or the API to create a recurring HTTP request.
Via dashboard:
- Navigate to Crons in the sidebar and click New Cron
- Enter a name (e.g., “Health Check”), your URL, select GET, and enter
*/5 * * * *as the cron expression - Set the alert threshold to 3 (notifies you after 3 consecutive failures)
- Click Create
Via API (curl):
curl -X POST https://app.recurohq.com/api/crons \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "name": "Health Check", "url": "https://api.yourapp.com/health", "method": "GET", "cron_expression": "*/5 * * * *", "timeout_seconds": 30, "alert_threshold": 3 }'For PHP, Node.js, and Python examples, see Creating a Cron Schedule.
Response:
{ "id": 42, "name": "Health Check", "cron_expression": "*/5 * * * *", "next_run_at": "2026-04-10T12:05:00+00:00", "is_active": true}The cron fires every 5 minutes immediately. Each execution is logged with the full HTTP response.
4. Push a one-off job
To schedule a single HTTP call (for example, after a user signs up), use the jobs endpoint.
Via dashboard: Navigate to Jobs > New Job, select a queue (or type a new name), enter the URL and payload, and click Create.
Via API (curl):
curl -X POST https://app.recurohq.com/api/jobs \ -H "Authorization: Bearer YOUR_API_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "queue": "notifications", "url": "https://api.yourapp.com/notify", "method": "POST", "payload": { "event": "user_signup", "user_id": 12345 } }'For PHP, Node.js, and Python examples, see Creating a Job.
The queue is created automatically if it does not exist. To delay the job by 30 minutes, add "delay": 1800.
5. Monitor executions
Go to Crons > [your cron] > Executions or Jobs in the sidebar to see the full history. Each execution shows:
- HTTP status code and response body
- Request and response headers
- Duration in milliseconds
- Failure reason (if applicable): timeout, connection error, DNS error, SSL error, assertion failure, or HTTP error
- Retry chain (for jobs with retries enabled)
6. Set up alerts
Alerts fire automatically based on your configuration:
- Crons: Set
alert_thresholdto 1, 2, or 3. After that many consecutive failures, you receive a failure alert. When the cron recovers, you receive a recovery alert. - Queues: Enable
alerts_enabledon the queue to get notified when jobs fail after all retries.
Configure your notification channel in Settings > Notifications — choose email, Slack, or Discord.
7. (Optional) Connect your AI agent
Recuro has an MCP server so AI agents can manage crons and jobs for you. Add this to your MCP config:
{ "mcpServers": { "recuro": { "command": "npx", "args": ["-y", "recuro-mcp"], "env": { "RECURO_API_TOKEN": "YOUR_API_TOKEN" } } }}Then ask your agent: “Create a cron that pings https://api.example.com/health every 5 minutes.”
See the MCP Server docs for the full tool reference.
Next steps
- Cron Schedules — Understand cron expressions, execution lifecycle, and assertions
- Queues — Learn about queue configuration, retries, and parallelism
- Create a Cron Job (API) — Full API reference for
POST /api/crons - Schedule a Job (API) — Full API reference for
POST /api/jobs - Webhook Signing — Verify that requests from Recuro are authentic