Update Worker Task
Method: PUT
Endpoint: /api/v2/worker-tasks/{workerTaskId}
Authentication: Supports Authorization: Bearer <YOUR_API_KEY>, api-key: <YOUR_API_KEY>, and ?token=<YOUR_API_KEY>. Prefer Bearer token.
Try it
Section titled “Try it”PUT
/api/v2/worker-tasks/{workerTaskId}Update worker taskAuthenticationRequired
Stored only in this browser tab. Sent only to https://openapi.coreclaw.com.
Parameters
Required
Saved Worker task template slug. Get it from the `data.list[].slug` field of `GET /api/v2/worker-tasks`. The playground prefills a sample slug; replace it with your own.
Request BodyRequiredapplication/json
FieldTypeRequiredDescription
descriptionstringOptionalTask description. Omit to keep current description.schedule_dayintegerOptionalDay of month for monthly schedule (1-31). Constraints: range 1-31.schedule_enabledenum: 0, 1OptionalSchedule switch. 0=disabled, 1=enabled. Constraints: allowed values: `0`, `1`.schedule_once_datestringOptionalOnce schedule date in YYYY-MM-DD.schedule_timestringOptionalSchedule time in HH:mm.schedule_typeenum: 1, 2, 3, 4OptionalSchedule type. 1=daily, 2=weekly, 3=monthly, 4=once. Constraints: allowed values: `1`, `2`, `3`, `4`.schedule_weekdayenum: 1, 2, 3, 4, 5, 6, 7OptionalWeekday for weekly schedule. 1=Monday ... 7=Sunday. Constraints: range 1-7; allowed values: `1`, `2`, `3`, `4`, `5`, `6`, `7`.titlestringOptionalTask title. Omit to keep current title.Request body (JSON)
When to use this endpoint
Section titled “When to use this endpoint”Use this endpoint to update the title, description, or schedule of a task template. Omitted fields keep their current values.
Identifier Notes
Section titled “Identifier Notes”workerTaskIdis the saved task template slug.
Path Parameters
Section titled “Path Parameters”| Parameter | Required | Type | Description |
|---|---|---|---|
workerTaskId | Yes | string | Saved Worker task template slug. Get it from the data.list[].slug field of GET /api/v2/worker-tasks. |
Request Body
Section titled “Request Body”Send the request body with Content-Type: application/json. Required/Optional describes each field; the Try it Request Body badge shows whether the body itself is required.
| Field | Required | Type | Description |
|---|---|---|---|
description | No | string | Task template description. Optional. |
schedule_day | No | integer | Day of month for monthly schedules (1-31). |
schedule_enabled | No | enum: 0, 1 | Schedule switch: 1 enabled, 0 disabled. |
schedule_once_date | No | string | Date for one-time schedules, YYYY-MM-DD. |
schedule_time | No | string | Schedule time of day, HH:mm. |
schedule_type | No | enum: 1, 2, 3, 4 | Schedule type: 1=daily, 2=weekly, 3=monthly, 4=once. |
schedule_weekday | No | enum: 1, 2, 3, 4, 5, 6, 7 | Day of week for weekly schedules (1=Monday … 7=Sunday). |
title | No | string | Task template title, used for display and search. |
JSON Example
Section titled “JSON Example”{ "description": "Scrape Google Maps business records on a schedule.", "schedule_day": 1, "schedule_enabled": 0, "schedule_once_date": "2026-08-01", "schedule_time": "09:00", "schedule_type": 1, "schedule_weekday": 1, "title": "Google Maps Scraper (Task)"}Request Example
Section titled “Request Example”curl -X PUT "https://openapi.coreclaw.com/api/v2/worker-tasks/YOUR_WORKER_TASK_ID" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ --data '{"description":"Scrape Google Maps business records on a schedule.","schedule_day":1,"schedule_enabled":0,"schedule_once_date":"2026-08-01","schedule_time":"09:00","schedule_type":1,"schedule_weekday":1,"title":"Google Maps Scraper (Task)"}'Response Example
Section titled “Response Example”{ "code": 0, "message": "success", "request_id": "req-123"}- API v2 supports Bearer token, the legacy
api-keyheader, and query token. Prefer Bearer token for new integrations. - PUT is a partial update: omitted fields keep their current values; you do not need to resend the whole task object.
- To update the task input parameters themselves (not the title or schedule), use
PUT /api/v2/worker-tasks/{workerTaskId}/input.
HTTP Responses
Section titled “HTTP Responses”| HTTP Status | Application Code | Meaning |
|---|---|---|
200 | 0 | OK |
400 | 11000 | Bad Request |
401 | 12001 | Unauthorized |
404 | 11004 | Not Found |
422 | 11000 | Unprocessable Entity |
429 | 13000 | Too Many Requests |
500 | 10000 | Internal Server Error |