Check that a list exists

head/lists/{listId}
Internal-Use Only

Checks for the existence of a list.

A successful response (for example, 200 OK) indicates that the list exists. An unsuccessful response (for example, 404 Not Found) indicates that the list does not exist.

Request Samples

1

Response Samples

1{
2 "version": 2,
3 "accept": "application/vnd.sas.listdata.list+json",
4 "count": 1,
5 "start": 0,
6 "limit": 10,
7 "name": "lists",
8 "items": [
9 {
10 "id": "3659ea38-2618-4474-aeac-0bf6cfd3c322",
11 "name": "list-a",
12 "creationTimeStamp": "2022-03-01T20:18:32Z",
13 "...see listResource object...": "..."
14 }
15 ],
16 "links": [
17 {
18 "href": "...",
19 "method": "...",
20 "rel": "...",
21 "uri": "..."
22 }
23 ]
24}

Path Parameters

NameTypeRequiredDescription
listId
string
true

A universally unique identifier for a list.

Examples:
"3659ea38-2618-4474-aeac-0bf6cfd3c322"

Header Parameters

NameTypeRequiredDescription
Accept
string
false

The desired response type.

Allowed values:
application/jsonapplication/vnd.sas.listdata.list+jsonapplication/vnd.sas.listdata.list+json;version=1application/vnd.sas.listdata.listdetails+jsonapplication/vnd.sas.listdata.listdetails.consumers+jsonapplication/vnd.sas.transfer.object+jsonapplication/vnd.sas.summary+json
Examples:
"application/json"

Responses

StatusMeaningDescription
200OKThe request succeeded.HeadersSchema
403ForbiddenThe user did not have the necessary permissions.Schema
404Not FoundNo item exists at the requested path.Schema
500Internal Server ErrorThe request could not be fulfilled because of an unexpected server error.Schema