post
/api/v2/reports/schedules/{id}/runRun a report schedule now.
Generates a local report artifact immediately from an enabled project-scoped schedule and records schedule-run delivery events. Live sender/object-storage delivery remains gated by provider configuration.
Requires bearer API key
Parameters
X-Project-Id
header
Required for organization-wide API keys on project-scoped endpoints. Project-scoped keys infer the project automatically.
Schema: string
id
path / required
No description provided.
Schema: string
Responses
202
Report schedule run accepted.
application/json{
"type": "object",
"additionalProperties": false,
"properties": {
"scheduleId": {
"type": "string"
},
"reportId": {
"type": "string"
},
"nextRunAt": {
"type": "string",
"format": "date-time"
},
"status": {
"type": "string",
"enum": [
"succeeded"
]
}
},
"required": [
"scheduleId",
"reportId",
"nextRunAt",
"status"
]
}404
Report schedule not found.
application/json{
"type": "object",
"properties": {
"error": {
"type": "string"
},
"message": {
"type": "string"
}
}
}409
Report schedule is paused.
application/json{
"type": "object",
"properties": {
"error": {
"type": "string"
},
"message": {
"type": "string"
}
}
}Try it
Send this request to the local WatchLLM REST handler. Use a key from `/workspace/api`; organization keys can include `X-Project-Id` only when the endpoint documents that header.