New: build custom CDF applications with Cognite Flows. Documentation · What's new.
curl --request GET \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/limits/values/{limitId} \
--header 'Authorization: Bearer <token>' \
--header 'cdf-version: <cdf-version>'{
"limitId": "atlas.monthly_ai_tokens",
"value": 1000
}Required capabilities:
projectsAcl:LIST
Retrieves a limit value by its limitId.
curl --request GET \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/limits/values/{limitId} \
--header 'Authorization: Bearer <token>' \
--header 'cdf-version: <cdf-version>'{
"limitId": "atlas.monthly_ai_tokens",
"value": 1000
}Documentation Index
Fetch the complete documentation index at: https://docs.cognite.com/llms.txt
Use this file to discover all available pages before exploring further.
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.
20230101-alpha Limits are identified by an id containg the service name and a service-scoped limit name.
For instance atlas.monthly_ai_tokens is the id of the atlas service limit monthly_ai_tokens.
Service and limit names are always inlower_snake_case.
The requested limit.
A singular representation of a Limit.
Limits are identified by an id containg the service name and a service-scoped limit name.
For instance atlas.monthly_ai_tokens is the id of the atlas service limit monthly_ai_tokens.
Service and limit names are always inlower_snake_case.
The numeric value of the limit.
Was this page helpful?