Skip to content
Optiwork API Docs

List the approvals of several files

POST
/drives/{drive}/approvals/list/batch
curl --request POST \
  --url https://work.optidata.cloud/api/drives/1/approvals/list/batch \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{ "node_ids": [ 665198, 665199 ] }'

Approvals for up to a hundred nodes in one call, each carrying its node, requester and approver. Folders are skipped. Every node involved is authorised individually — lacking view on any of them fails the whole request.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “ Parameters ”

Path Parameters

Section titled “Path Parameters”
drive
required
integer format: int64

Numeric id of the drive. Read it from GET /drives/config.json.

Request Bodyrequired

Section titled “Request Bodyrequired”
Media typeapplication/json
object
node_ids
required
Array<integer>
>= 1 items <= 100 items
Examples
Examplebatch
{
  "node_ids": [
    665198,
    665199
  ]
}

Responses

Section titled “ Responses ”

200

Section titled “200”

The approvals found.

Media typeapplication/json
Array<object>

A request asking a specific user to approve or reject a file. Folders cannot carry approvals.

object
id
integer format: int64
node_id
integer format: int64
requester_user_id
integer format: int64
requested_user_id
integer | null format: int64
requested_user_email

Set when the approver is addressed by e-mail rather than by id.

string | null format: email
status
string
Allowed values: pending approved rejected
requester_user_note
string | null
<= 1000 characters
comment

Optional note left by the approver.

string | null
<= 255 characters
rejection_reason
string | null
<= 255 characters
is_download_allowed
boolean | null
is_rejection_reason_required
boolean | null
edit_mode
One of:

Whether the file stays editable while the approval is open (released) or is frozen until it is decided (blocked).

string
Allowed values: blocked released
expires_at
string | null format: date-time
created_at
string format: date-time
updated_at
string format: date-time
requesterUser
One of:

Compact representation of a user, embedded in other payloads.

object
id
integer format: int64
uuid

Tenant-wide identifier of the user. Use this, not id, on account endpoints.

string format: uuid
name
string
email
string format: email
status

Present where the payload includes it (for example audit entries).

string
Allowed values: active inactive blocked
deleted_at
string | null format: date-time
avatar_url
string | null format: uri
full_name
string
requestedUser
One of:

Compact representation of a user, embedded in other payloads.

object
id
integer format: int64
uuid

Tenant-wide identifier of the user. Use this, not id, on account endpoints.

string format: uuid
name
string
email
string format: email
status

Present where the payload includes it (for example audit entries).

string
Allowed values: active inactive blocked
deleted_at
string | null format: date-time
avatar_url
string | null format: uri
full_name
string
Example
[
  {
    "status": "pending",
    "edit_mode": "blocked",
    "requesterUser": {
      "id": 15,
      "uuid": "9c1f0e2a-4d31-4d8a-8c1a-1f0b6b1f9a10",
      "name": "Jane Doe",
      "email": "jane.doe@acme.example",
      "status": "active"
    },
    "requestedUser": {
      "id": 15,
      "uuid": "9c1f0e2a-4d31-4d8a-8c1a-1f0b6b1f9a10",
      "name": "Jane Doe",
      "email": "jane.doe@acme.example",
      "status": "active"
    }
  }
]

401

Section titled “401”

Missing, malformed or expired authentication key.

Media typeapplication/json

Authentication failures use an error key rather than message.

object
error
required
string
Examples
Examplemissing

No bearer token sent

{
  "error": "JWT passport exception: Missing bearer token in request"
}

403

Section titled “403”

The caller lacks the permission level the operation requires.

Media typeapplication/json

Generic error envelope used by policy, binding and framework failures.

object
message
required

Human-readable description of the failure.

string
Examples
Exampledenied
{
  "message": "This action is unauthorized."
}

422

Section titled “422”

The request body or query string failed validation.

Media typeapplication/json
object
message
required

The first validation message.

string
errors
required

Validation messages keyed by field name.

object
key
additional properties
Array<string>
Examples
Exampleinvalid
{
  "message": "The name field is required.",
  "errors": {
    "name": [
      "The name field is required."
    ]
  }
}

429

Section titled “429”

Rate limit exceeded. Retry after the window resets.

Media typeapplication/json

Generic error envelope used by policy, binding and framework failures.

object
message
required

Human-readable description of the failure.

string
Examples
Examplethrottled
{
  "message": "Too Many Attempts."
}