Authorizations
API key for authentication. Get your API key from the Cronhost dashboard.
Path Parameters
Unique schedule identifier
Example:
"schedule_123"
curl --request POST \
--url https://cronho.st/api/v1/schedules/{id}/trigger \
--header 'x-api-key: <api-key>'{
"data": {
"id": "job_456",
"scheduleId": "schedule_123",
"status": "SUCCESS",
"scheduledRunAtUtc": "2024-01-14T14:00:00.000Z",
"attemptNumber": 1,
"httpMethod": "GET",
"endpoint": "https://api.example.com/health",
"body": "{\"key\": \"value\"}",
"headers": "{\"User-Agent\": \"Cronhost-Monitor\"}",
"statusCode": 200,
"response": "{\"status\": \"ok\"}",
"startedAtUtc": "2024-01-14T14:00:01.000Z",
"completedAtUtc": "2024-01-14T14:00:02.500Z",
"errorMessage": "Request timeout after 30 seconds",
"createdAt": "2024-01-14T14:00:00.000Z",
"updatedAt": "2024-01-14T14:00:02.500Z"
},
"success": true,
"message": "Schedule triggered successfully"
}Manually trigger a schedule to run immediately, regardless of its cron schedule. Creates a new job that will execute the HTTP request.
curl --request POST \
--url https://cronho.st/api/v1/schedules/{id}/trigger \
--header 'x-api-key: <api-key>'{
"data": {
"id": "job_456",
"scheduleId": "schedule_123",
"status": "SUCCESS",
"scheduledRunAtUtc": "2024-01-14T14:00:00.000Z",
"attemptNumber": 1,
"httpMethod": "GET",
"endpoint": "https://api.example.com/health",
"body": "{\"key\": \"value\"}",
"headers": "{\"User-Agent\": \"Cronhost-Monitor\"}",
"statusCode": 200,
"response": "{\"status\": \"ok\"}",
"startedAtUtc": "2024-01-14T14:00:01.000Z",
"completedAtUtc": "2024-01-14T14:00:02.500Z",
"errorMessage": "Request timeout after 30 seconds",
"createdAt": "2024-01-14T14:00:00.000Z",
"updatedAt": "2024-01-14T14:00:02.500Z"
},
"success": true,
"message": "Schedule triggered successfully"
}API key for authentication. Get your API key from the Cronhost dashboard.
Unique schedule identifier
"schedule_123"