List instruction versions
Full version history for a project and task, newest first, including each version's text and what caused it.
Authorization
webhookToken Workspace webhook token from Settings -> Integrations.
In: header
Query Parameters
Project name - must match the project used when creating logs.
Task name - must match the task used when creating logs.
Response Body
application/json
application/json
curl -X GET "https://example.com/api/instructions/versions?project=string&task=string"{ "versions": [ { "id": "string", "version": 0, "content": "string", "source": "seed", "teachComment": "string", "logId": "string", "createdBy": "string", "createdAt": "2019-08-24T14:15:22Z", "isActive": true } ]}{ "error": "string", "code": "string", "fields": { "property1": "string", "property2": "string" }}Get or seed instructions POST
Fetches the active instructions, creating them first when none exist. Call this at the start of an automation run: if the doc is missing and `default` is provided, the default becomes version 1 (`source: seed`) and is returned - so a shipped template works with zero setup. When the doc exists, `default` is ignored and the stored text always wins.
Save a new instructions version POST
Appends a version and makes it active. Token callers create a `teach` version - use after a reviewer sends a draft back with feedback: rewrite the instructions with your own AI step, then save the result here with the reviewer's comment and the log it came from. Dashboard sessions create `manual` edits or restores.