Create Manual Snapshot
const url = 'https://aura-api-eu.strangeworks.com/api/v1/projects/example/snapshots';const options = { method: 'POST', headers: {Authorization: 'Bearer <token>', 'Content-Type': 'application/json'}, body: '{"label":"example"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://aura-api-eu.strangeworks.com/api/v1/projects/example/snapshots \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --data '{ "label": "example" }'Capture the live run workspace as a snapshot, on the user’s initiative.
Solve snapshots are recorded automatically when a run completes; this is
the user-decided “keep this state” capture (kind="manual", no linked
execution). Only meaningful once the project is in run mode — before that
there is no run workspace worth freezing. Refused with a 409 while a checkout
is rewriting the tree: a capture taken then would freeze a state the workspace
never held.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”Responses
Section titled “Responses”Successful Response
Metadata for a single workspace snapshot (list view).
Built from the Snapshot ORM object via model_validate; solution_summary
is read from the model’s like-named property (the linked execution’s summary), so
the execution relationship must be eager-loaded.
object
Whether the live workspace sits on this snapshot: the basis set by the latest solve or checkout.
Example
{ "is_current": false, "kind": "solve", "tags": []}Validation Error
object
object
object
Examplegenerated
{ "detail": [ { "ctx": {}, "input": "example", "loc": [ "example" ], "msg": "example", "type": "example" } ]}