ReferenceAPI
curl -X GET "https://api.nevia.cloud/v1/operations?workspace=01d4cnjjq40hnnh0nwmkg35nv2h" \
-H "Authorization: Bearer $TOKEN"{
"operations": [
{
"id": "01d4cnjm89yk0r3xtv80dy0x7by",
"workspace": "01d4cnjjq40hnnh0nwmkg35nv2h",
"resource_type": "computer",
"resource": "01d4cnjk3xg90y576w8y6t4gdwm",
"type": "computer.create",
"state": "running",
"error": null,
"created_at": "2026-09-10T12:34:56Z",
"updated_at": "2026-09-10T12:34:58Z",
"finished_at": null
}
],
"next_cursor": "string",
"has_more": true
}Authorization
bearerAuth Authorization
Bearer <token>
Send the token in the Authorization: Bearer <token> header. See Authenticate.
In: header
Query Parameters
workspace*
string
Workspace id or exact name
limit?
integer
Page size
Range
1 <= value <= 100Default
50cursor?
string
next_cursor from the previous page
resource?
string
Computer, database or checkpoint id
Match
^[A-Za-z0-9_-]{1,64}$state?
string
running · finished · failedBehavior
Paging with has_more walks back in time. You can reach operations whose workspace is gone only by id.
Response
application/jsonOperations started by the workspace's resources, newest first.