Request Scheduling

Download Page (.md)

Scheduling API lets you create, manage, and monitor cron-based recurring HTTP requests. Schedules persist across server restarts and can be enabled or disabled without deletion. Use these endpoints when you need to collect data periodically, run health checks, generate scheduled reports, or trigger any repeatable HTTP task.

`GET /api/v1/curl/schedule`

Retrieve a paginated list of all recurring schedules, sorted by creation time (newest first). Each entry shows its schedule configuration, next execution time, and current state.

A schedule can be in one of two states:

Enabled — Active, will execute at the next scheduled time.
Disabled — Paused, will not execute (can be re-enabled).

Parameters

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

cURL
SDK

curl -X GET "https://proj_a1b2c3d4-ctnr_e5f6g7h8-curl-1.eu-west-1.containers.hoody.icu/api/v1/curl/schedule?page=1&limit=20" \
  -H "Authorization: Bearer &lt;token&gt;"

await client.curl.schedules.listIterator({ page: 1, limit: 20 })

Response

{
  "items": [
    {
      "id": "7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f",
      "name": "Daily health check",
      "cron": "0 0 9 * * MON-FRI",
      "enabled": true,
      "request": {
        "url": "https://api.example.com/health",
        "method": "GET"
      },
      "created_at": "2024-03-15T10:30:00Z",
      "last_run": "2024-03-18T09:00:00Z",
      "next_run": "2024-03-19T09:00:00Z"
    }
  ],
  "meta": {
    "page": 1,
    "limit": 20,
    "total": 1
  }
}

{
  "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

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

Retrieve complete details of a specific schedule including its cron expression, request configuration, and execution history.

Parameters

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

cURL
SDK

curl -X GET "https://proj_a1b2c3d4-ctnr_e5f6g7h8-curl-1.eu-west-1.containers.hoody.icu/api/v1/curl/schedule/7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f" \
  -H "Authorization: Bearer &lt;token&gt;"

await client.curl.schedules.get("7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f")

Response

{
  "id": "7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f",
  "name": "Daily health check",
  "cron": "0 0 9 * * MON-FRI",
  "enabled": true,
  "request": {
    "url": "https://api.example.com/health",
    "method": "GET",
    "headers": {
      "Accept": "application/json"
    }
  },
  "created_at": "2024-03-15T10:30:00Z",
  "last_run": "2024-03-18T09:00:00Z",
  "next_run": "2024-03-19T09:00:00Z"
}

{
  "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 the list schedules endpoint

{
  "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

`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.

Cron expression format: 6 fields — second minute hour day month weekday.

Expression	Meaning
`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 include periodic API data collection, regular health checks and monitoring, scheduled report generation, and automated backups or synchronization.

Request body

Field	Type	Required	Description
`cron`	string	Yes	Six-field cron expression (`second minute hour day month weekday`).
`request`	object	Yes	The HTTP request configuration to execute on each tick. Mirrors the full cURL request schema (URL, method, headers, auth, etc.).

cURL
SDK

curl -X POST "https://proj_a1b2c3d4-ctnr_e5f6g7h8-curl-1.eu-west-1.containers.hoody.icu/api/v1/curl/schedule" \
  -H "Authorization: Bearer &lt;token&gt;" \
  -H "Content-Type: application/json" \
  -d '{
    "cron": "0 0 9 * * MON-FRI",
    "request": {
      "url": "https://api.example.com/health",
      "method": "GET",
      "headers": {
        "Accept": "application/json"
      }
    }
  }'

await client.curl.schedules.create({
  cron: "0 0 9 * * MON-FRI",
  request: {
    url: "https://api.example.com/health",
    method: "GET",
    headers: {
      "Accept": "application/json"
    }
  }
})

Response

The schedule was created successfully and activated. Use GET /api/v1/curl/schedule/{id} to inspect the returned configuration.

{
  "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 the 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

{
  "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

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

Enable or disable a schedule without deleting it. Send a JSON body with an enabled boolean — {"enabled": true} activates the schedule and {"enabled": false} pauses it.

Parameters

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

Request body

Field	Type	Required	Description
`enabled`	boolean	Yes	Set to `true` to enable the schedule or `false` to disable it.

cURL
SDK

curl -X PATCH "https://proj_a1b2c3d4-ctnr_e5f6g7h8-curl-1.eu-west-1.containers.hoody.icu/api/v1/curl/schedule/7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f/toggle" \
  -H "Authorization: Bearer &lt;token&gt;" \
  -H "Content-Type: application/json" \
  -d '{"enabled": false}'

await client.curl.schedules.toggle("7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f", { enabled: false })

Response

The schedule state was toggled successfully. Subsequent calls to GET /api/v1/curl/schedule/{id} will reflect the new enabled value.

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

Error Code	Title	Description	Resolution
`SCHEDULE_NOT_FOUND`	Schedule does not exist	Cannot toggle a schedule that does not exist	Verify schedule ID using the list schedules endpoint

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

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

`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

cURL
SDK

curl -X DELETE "https://proj_a1b2c3d4-ctnr_e5f6g7h8-curl-1.eu-west-1.containers.hoody.icu/api/v1/curl/schedule/7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f" \
  -H "Authorization: Bearer &lt;token&gt;"

await client.curl.schedules.delete("7f8e9d0c-1b2a-3c4d-5e6f-7a8b9c0d1e2f")

Response

The schedule was deleted successfully. The ID is now free to be reused and any pending executions are cancelled.

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

Error Code	Title	Description	Resolution
`SCHEDULE_NOT_FOUND`	Schedule does not exist	Cannot delete a schedule that does not exist	Verify schedule ID using the list schedules endpoint

{
  "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 the operation