Base URL
API key scopes
Every endpoint uses one scope.
Create a workspace API key under Settings > Workspace > Products > API. A personal API key can include Scheduled Tasks API when your admin allows it. See Personal API keys.
A workspace key runs as its service account. A personal key runs as the member who owns it. Scheduled Tasks must be enabled for the workspace, and that owner must have access. General access covers the owner. Member access covers the owner only when the owner or one of their groups is included.
Each task is owned by the member or service account that created it. The key sees and changes that owner’s tasks. A personal key also sees tasks the member created in the product. A workspace can hold 10 tasks per owner. The 11th create returns
400 with AUTOMATION_LIMIT_REACHED.
If a service account no longer has a live key with AUTOMATION_API, its active tasks that are not MANUAL are paused. A workspace key you create under Settings > Workspace > Products > API gets a new service account, so it can’t see those tasks or keep them running. Recreate them with that key. Rotating a workspace key keeps the same service account, so those tasks keep running. Revoking a personal key leaves that member’s tasks running. MANUAL tasks have no clock, so this pause does not change them.
Available endpoints
Scheduled task object
List and get includerunCount. Create, update, pause, and resume return the same object without runCount.
updatedAt field.
Schedule
timeOfDay uses 24 hour HH:mm. A missing or invalid clock for a scheduled frequency returns 400.
Context on the task
assistantId is the primary agent. It must be available to the key, or create and update return 403 with AUTOMATION_TAG_ACCESS_DENIED:assistant:{id}.
modelMode EXPLICIT requires modelId in the same request. The model must be selectable for that member or service account. Otherwise the response is 403 with AUTOMATION_TAG_ACCESS_DENIED:model:missing or AUTOMATION_TAG_ACCESS_DENIED:model:{id}. AUTO and UNSET store modelId as null. If you omit modelMode and send modelId, the task is stored as EXPLICIT. If you omit both, it is stored as UNSET.
Tagged integrations, folders, workflows, skills, and taggedAssistantId that the key cannot use are dropped on save. They do not fail the request. attachmentIds must already belong to that member or service account in this workspace. An attachment that owner does not have returns 403 with AUTOMATION_TAG_ACCESS_DENIED:attachment:unknown.
Each tag array accepts at most 20 values. Each skill slug is at most 100 characters. attachmentIds accepts at most 20 ids.
Rate limits
The Scheduled Tasks API follows standard API rate limits. If you exceed the limit, you receive a429 response. Wait and retry with exponential backoff.
Langdock intentionally blocks browser-origin requests to protect your API key and ensure your applications remain secure. For more information, please see our guide on API Key Best Practices.