Request Scheduling

Use the Request Scheduling API to create and manage recurring HTTP requests driven by cron expressions. Schedules persist across container restarts and execute their configured request payload at the configured cadence. Use these endpoints to build monitoring, reporting, and synchronization jobs without manual intervention.

Two states are supported for every schedule:

• Enabled — Active and will execute at the next scheduled time.
• Disabled — Paused; does not execute but can be re-enabled.

Note

All endpoints in this section target the curl service inside your container. Replace {projectId} and {containerId} in the hostname with your real identifiers, and {server} with the region code (for example node-us).

Schedules

GET /api/v1/curl/schedule

List every recurring schedule, sorted by creation time with the newest first. Each entry includes its cron expression, request configuration, and execution state.

Parameters

Name	In	Type	Required	Description
page	query	integer	No	1-based page number
limit	query	integer	No	Items per page; current handler returns all items when omitted

Response

200

{
  "items": [
    {
      "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "name": "API health monitor",
      "cron": "0 */5 * * * *",
      "enabled": true,
      "created_at": "2026-01-15T10:30:00Z",
      "next_run": "2026-01-15T10:35:00Z",
      "last_run": "2026-01-15T10:30:00Z",
      "request": {
        "url": "https://api.example.com/health",
        "method": "GET",
        "headers": {
          "X-Monitor": "hoody"
        },
        "timeout": 30
      }
    }
  ],
  "meta": {
    "page": 1,
    "limit": 20,
    "total": 1
  }
}

500

{
  "error": "STORAGE_ERROR",
  "message": "Failed to read schedules"
}

Error Code	Title	Description	Resolution
STORAGE_ERROR	Storage read failed	Unable to read schedules from persistent storage	Check storage directory permissions and disk availability

SDK Usage

cURL

curl https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com/api/v1/curl/schedule?page=1&limit=20

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({
  baseURL: 'https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com',
  token: process.env.HOODY_TOKEN,
});

const page = await client.curl.schedules.listIterator({ page: 1, limit: 20 });
for await (const schedule of page) {
  console.log(schedule.id, schedule.cron);
}

GET /api/v1/curl/schedule/{id}

Retrieve complete details for a single schedule, including its cron expression, request configuration, and last/next execution timestamps.

Parameters

Name	In	Type	Required	Description
id	path	string	Yes	Unique schedule identifier (UUID format)

Response

200

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "name": "API health monitor",
  "cron": "0 */5 * * * *",
  "enabled": true,
  "created_at": "2026-01-15T10:30:00Z",
  "next_run": "2026-01-15T10:35:00Z",
  "last_run": "2026-01-15T10:30:00Z",
  "request": {
    "url": "https://api.example.com/health",
    "method": "GET",
    "headers": {
      "X-Monitor": "hoody"
    },
    "timeout": 30
  }
}

404

{
  "error": "SCHEDULE_NOT_FOUND",
  "message": "Schedule not found"
}

Error Code	Title	Description	Resolution
SCHEDULE_NOT_FOUND	Schedule does not exist	No schedule found with the provided ID	Verify schedule ID using GET /api/v1/curl/schedule

500

{
  "error": "STORAGE_ERROR",
  "message": "Failed to read schedule"
}

Error Code	Title	Description	Resolution
STORAGE_ERROR	Storage read failed	Failed to read schedule data from storage	Check storage integrity and retry

SDK Usage

cURL

curl https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com/api/v1/curl/schedule/a1b2c3d4-e5f6-7890-abcd-ef1234567890

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({
  baseURL: 'https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com',
  token: process.env.HOODY_TOKEN,
});

const schedule = await client.curl.schedules.get('a1b2c3d4-e5f6-7890-abcd-ef1234567890');

POST /api/v1/curl/schedule

Create a new cron-based schedule that executes an HTTP request repeatedly at specified intervals. Schedules are persistent and survive server restarts.

Tip

Cron expressions use 6 fields: second minute hour day month weekday. Examples:

• 0 * * * * * — every minute
• 0 0 * * * * — every hour
• 0 0 9 * * MON-FRI — weekdays at 9 AM
• 0 0 0 * * * — daily at midnight
• 0 0 12 1 * * — monthly on the 1st at noon

Common use cases:

• Periodic API data collection
• Regular health checks and monitoring
• Scheduled report generation
• Automated backups or synchronization

Request Body

Name	Type	Required	Description
cron	string	Yes	Six-field cron expression: second minute hour day month weekday
request	object	Yes	The HTTP request to execute on each tick. url is required; see curl_CurlRequest for the full field list

{
  "cron": "0 */5 * * * *",
  "request": {
    "url": "https://api.example.com/health",
    "method": "GET",
    "headers": {
      "X-Monitor": "hoody"
    },
    "timeout": 30
  }
}

Response

201

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "name": null,
  "cron": "0 */5 * * * *",
  "enabled": true,
  "created_at": "2026-01-15T10:30:00Z",
  "next_run": "2026-01-15T10:35:00Z",
  "last_run": null,
  "request": {
    "url": "https://api.example.com/health",
    "method": "GET",
    "headers": {
      "X-Monitor": "hoody"
    },
    "timeout": 30
  }
}

400

{
  "error": "INVALID_CRON_EXPRESSION",
  "message": "Invalid cron expression: invalid field"
}

Error Code	Title	Description	Resolution
INVALID_CRON_EXPRESSION	Malformed cron expression	The provided cron expression is invalid or incorrectly formatted	Use 6-field format: second minute hour day month weekday. Example: 0 0 9 * * MON-FRI
INVALID_PARAMETER	Invalid request configuration	The embedded request contains invalid parameters	Verify request.url is valid and all parameters match expected types

500

{
  "error": "SCHEDULE_CREATION_FAILED",
  "message": "Failed to create schedule"
}

Error Code	Title	Description	Resolution
SCHEDULE_CREATION_FAILED	Schedule creation failed	Unable to create schedule in persistent storage	Check storage permissions and disk space, then retry

SDK Usage

cURL

curl -X POST https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com/api/v1/curl/schedule \
  -H "Content-Type: application/json" \
  -d '{
    "cron": "0 */5 * * * *",
    "request": {
      "url": "https://api.example.com/health",
      "method": "GET",
      "headers": { "X-Monitor": "hoody" },
      "timeout": 30
    }
  }'

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({
  baseURL: 'https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com',
  token: process.env.HOODY_TOKEN,
});

const schedule = await client.curl.schedules.create({
  cron: '0 */5 * * * *',
  request: {
    url: 'https://api.example.com/health',
    method: 'GET',
    headers: { 'X-Monitor': 'hoody' },
    timeout: 30,
  },
});

PATCH /api/v1/curl/schedule/{id}/toggle

Toggle a schedule between enabled and disabled without deleting it.

Parameters

Name	In	Type	Required	Description
id	path	string	Yes	Unique schedule identifier

Request Body

Name	Type	Required	Description
enabled	boolean	Yes	true to enable the schedule, false to disable it

{
  "enabled": false
}

Response

200

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "enabled": false
}

404

{
  "error": "SCHEDULE_NOT_FOUND",
  "message": "Schedule not found"
}

Error Code	Title	Description	Resolution
SCHEDULE_NOT_FOUND	Schedule does not exist	Cannot toggle schedule that doesn’t exist	Verify schedule ID using GET /api/v1/curl/schedule

500

{
  "error": "STORAGE_ERROR",
  "message": "Failed to toggle schedule"
}

Error Code	Title	Description	Resolution
STORAGE_ERROR	Storage update failed	Schedule exists but state could not be updated in storage	Check storage permissions and retry operation

SDK Usage

cURL

curl -X PATCH https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com/api/v1/curl/schedule/a1b2c3d4-e5f6-7890-abcd-ef1234567890/toggle \
  -H "Content-Type: application/json" \
  -d '{"enabled": false}'

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({
  baseURL: 'https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com',
  token: process.env.HOODY_TOKEN,
});

await client.curl.schedules.toggle('a1b2c3d4-e5f6-7890-abcd-ef1234567890', { enabled: false });

DELETE /api/v1/curl/schedule/{id}

Permanently delete a recurring schedule. The schedule immediately stops executing and all configuration is removed.

Parameters

Name	In	Type	Required	Description
id	path	string	Yes	Unique schedule identifier

Response

200

{
  "id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "deleted": true
}

404

{
  "error": "SCHEDULE_NOT_FOUND",
  "message": "Schedule not found"
}

Error Code	Title	Description	Resolution
SCHEDULE_NOT_FOUND	Schedule does not exist	Cannot delete schedule that doesn’t exist	Verify schedule ID using GET /api/v1/curl/schedule

500

{
  "error": "STORAGE_ERROR",
  "message": "Failed to delete schedule"
}

Error Code	Title	Description	Resolution
STORAGE_ERROR	Storage delete failed	Schedule exists but could not be deleted from storage	Check storage permissions and retry operation

SDK Usage

cURL

curl -X DELETE https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com/api/v1/curl/schedule/a1b2c3d4-e5f6-7890-abcd-ef1234567890

TypeScript SDK

import { HoodyClient } from 'hoody-sdk';

const client = new HoodyClient({
  baseURL: 'https://{projectId}-{containerId}-curl-1.{server}.containers.hoody.com',
  token: process.env.HOODY_TOKEN,
});

await client.curl.schedules.delete('a1b2c3d4-e5f6-7890-abcd-ef1234567890');