listContentReviews

GET

/api/v1/content-reviews

const url = 'https://example.com/api/v1/content-reviews';
const options = {method: 'GET'};

try {
  const response = await fetch(url, options);
  const data = await response.json();
  console.log(data);
} catch (error) {
  console.error(error);
}

curl --request GET \
  --url https://example.com/api/v1/content-reviews

List content reviews, optionally filtered by state. Anyone who can author content can see where it stands. Requires an authenticated dashboard user with the read scope.

Parameters

Query Parameters

state

string

Responses

200

Content reviews

application/json

object

data

required

Legacy current-revision queue. New Studio actions use content submissions; this compatibility route still reports the server-side assignment gate.

object

required

required

boolean

items

required

Array<object>

One piece of content and where it stands. State is pending, approved, or rejected, derived from whether a decision exists for this exact revision.

object

contentType

required

string

Allowed values: playlist layout

contentId

required

string format: uuid

name

required

string

revision

required

integer format: int64

state

required

string

Allowed values: pending approved rejected

assignedScreens

required

integer

updatedAt

required

string format: date-time

authorName

string

lastNote

string

lastReviewedAt

string format: date-time

Example

{
  "data": {
    "items": [
      {
        "contentType": "playlist",
        "state": "pending"
      }
    ]
  }
}

401

Dashboard authentication required

403

Insufficient role