Skip to main content
GET
/
processes
/
signals
/
sinks
List sinks
curl --request GET \
  --url https://{cluster}.cognitedata.com/api/v1/projects/{project}/processes/signals/sinks \
  --header 'Authorization: Bearer <token>'
{
  "items": [
    {
      "type": "email",
      "externalId": "my.known.id",
      "emailAddress": "<string>",
      "createdTime": 1730204346000,
      "lastUpdatedTime": 1730204346000
    }
  ],
  "nextCursor": "<string>"
}

Authorizations

Authorization
string
header
required

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.

Query Parameters

limit
integer
default:100

Limits the number of results to be returned. The maximum results returned by the server is 1000 even if you specify a higher limit.

Required range: 1 <= x <= 1000
cursor
string

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.

Example:

"4zj0Vy2fo0NtNMb229mI9r1V3YG5NBL752kQz1cKtwo"

Response

List of sinks and an optional cursor.

items
(EmailSinkWrite · object | UserSinkWrite · object)[]
required
Required array length: 1 - 100 elements

Description of an e-mail sink.

nextCursor
string

Cursor for retrieving the next page of results. Omitted if there are no more results.

Last modified on April 23, 2026