Skip to content
Recuro Docs

Introduction

Recuro is an HTTP job scheduling platform that lets you fire HTTP requests on a cron schedule or push one-off jobs to a queue — with automatic retries, failure alerts, webhook signing, and full execution history.

Who is Recuro for?

Recuro is built for developers and teams who need reliable scheduled HTTP requests without managing infrastructure. Common use cases:

  • Health checks — Ping your endpoints every minute and get alerted on failures
  • Data pipelines — Trigger nightly ETL jobs, report generation, or cache warming
  • Webhook fanout — Distribute events to multiple endpoints with retry guarantees
  • Delayed tasks — Schedule one-off HTTP calls for the future (send a reminder in 30 minutes, expire a token in 24 hours)
  • Background processing — Offload work from your app server to a queue with configurable retries and dead-letter handling

Key features

  • Cron schedules — Recurring HTTP requests with any standard 5-field cron expression. Every execution is logged with status codes, response body, headers, and timing.
  • Queue-based jobs — Push one-off HTTP tasks via the API. Jobs run immediately or after a configurable delay.
  • Automatic retries — Failed jobs are retried with configurable delays (default: 1 min, 30 min, 3 hours). Jobs that exhaust all retries land in a dead-letter queue.
  • Success assertions — Define conditions (status code, response body, JSON path, response time) that must pass for an execution to be considered successful.
  • Failure alerts — Get notified via email, Slack, or Discord when jobs fail beyond a threshold, and again when they recover.
  • Webhook signing — Every outbound request can be signed with HMAC-SHA256 so your endpoints can verify authenticity.
  • Completion callbacks — Receive a POST to your callback URL after each execution completes (success or failure).
  • Team collaboration — Invite your team and manage access with admin and member roles.
  • Maintenance windows — Suppress alerts during planned downtime.
  • MCP server — Connect Recuro to AI agents (Claude, Cursor, Windsurf) and manage crons and jobs through natural language.

How it works

  1. Create a cron or queue in the dashboard or via the API
  2. Recuro fires HTTP requests on schedule — calling your endpoint with the configured method, headers, and payload
  3. Monitor executions — See full history with response times, status codes, request/response bodies, and failure reasons
  4. Get alerted — If a job fails repeatedly, you receive a notification. When it recovers, you get a recovery alert.

Core concepts

ConceptDescription
Cron ScheduleA recurring HTTP request that fires on a cron expression
QueueA named container for one-off jobs with shared retry and timeout settings
JobA single HTTP request queued for execution
RunThe execution record for a job, capturing the HTTP response and timing
AlertA notification triggered by failures or recoveries
TeamAn organization unit that owns crons, queues, and jobs

API overview

Recuro has two public API endpoints. Both require a Bearer token from Settings > API.

EndpointDescription
POST /api/cronsCreate a recurring cron job
POST /api/jobsPush a one-off job to a queue

Next steps