Create an update content state job

post/lists/{listId}/updateContentStateJobs

Internal-Use Only

Updates the state for every row in a list.

Optionally, you can update the expiry of the selected rows when they are being deployed, if they were previously in developing. If an expiry is listed but the action is to move to developing, no expiries are changed.

The expiry value of a row is represented as a UNIX timestamp, which is the number of seconds since the UNIX epoch (January 1, 1970).

If the value for the 'exactExpiry' property is 'true', the value provided is taken to be a UNIX timestamp and is used directly. Otherwise, it is used as an offset, which is the number of seconds after now that the rows should expire.

You can create a new update content state job only if there are no other jobs running on that list.

You cannot create an update content state job for an immutable list.

You must specify in the request body whether the rows are to be moved to deployed or moved to developing.

Request Samples

application/json
1

Response Samples

202
application/json
1{
2  "id": "b791e348-984e-439d-bff4-5b4163d897af",
3  "version": 1,
4  "state": "completed",
5  "creationTimeStamp": "2022-05-31T14:31:57Z",
6  "createdBy": "userA",
7  "completedTimeStamp": "2022-05-31T14:32:57Z",
8  "listId": "3659ea38-2618-4474-aeac-0bf6cfd3c322",
9  "totalErrors": 1,
10  "results": {
11    "recordCount": 100
12  },
13  "errors": [
14    {
15      "message": "string",
16      "id": "string",
17      "errorCode": 0,
18      "httpStatusCode": 0,
19      "details": [
20        "string"
21      ],
22      "remediation": "string",
23      "version": 2
24    }
25  ],
26  "links": [
27    {
28      "href": "...",
29      "method": "...",
30      "rel": "...",
31      "uri": "..."
32    }
33  ]
34}

Path Parameters

Name	Type	Required	Description
listId	string	true	A universally unique identifier for a purge job.

Request Body

Name	Type	Required	Description
items	array [object]	false

Responses

Status	Meaning	Description
202	Accepted	The request has been accepted for processing, but the processing has not been completed.	Headers	Schema
400	Bad Request	The request was invalid.		Schema
403	Forbidden	The user did not have the necessary permissions.		Schema
404	Not Found	No item exists at the requested path.		Schema
409	Conflict	The request could not be completed due to a conflict with an existing resource.		Schema
500	Internal Server Error	The request could not be fulfilled because of an unexpected server error.		Schema