const labels = await client.labels.list({ filter: { externalIdPrefix: 'Pu'}});{
"items": [
{
"externalId": "my.known.id",
"name": "<string>",
"createdTime": 1730204346000,
"description": "<string>",
"dataSetId": 4503599627370496
}
],
"nextCursor": "<string>"
}Required capabilities:
labelsAcl:READ
Use advanced filtering options to find label definitions.
const labels = await client.labels.list({ filter: { externalIdPrefix: 'Pu'}});{
"items": [
{
"externalId": "my.known.id",
"name": "<string>",
"createdTime": 1730204346000,
"description": "<string>",
"dataSetId": 4503599627370496
}
],
"nextCursor": "<string>"
}Authorizations
Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to accept OpenID Connect tokens. Use a header key of 'Authorization' with a value of 'Bearer $accesstoken'. The token can be obtained through any flow supported by the identity provider.
Body
Cursor for paging through results. In general, if a response contains a nextCursor
property, it means that there may be more results, and you should pass that value as the
cursor parameter in the next request.
Note that the cursor may or may not be encrypted, but either way, it is not intended to be decoded. Its internal structure is not a part of the public API, and may change without notice. You should treat it as an opaque string and not attempt to craft your own cursors.
Was this page helpful?