curl --request POST \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/extractors/solutions/byids \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"items": [
{
"externalId": "my.known.id"
}
],
"ignoreUnknownIds": true
}
'{
"items": [
{
"externalId": "my.known.id",
"name": "<string>",
"sourceSystemExternalId": "<string>",
"documentation": "<string>",
"type": "global",
"extractorExternalId": "<string>"
}
]
}Retrieve solutions by external ID. Solutions connect sources to extractors, documenting how a specific extractor might be used to connect to a source system.
curl --request POST \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/extractors/solutions/byids \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"items": [
{
"externalId": "my.known.id"
}
],
"ignoreUnknownIds": true
}
'{
"items": [
{
"externalId": "my.known.id",
"name": "<string>",
"sourceSystemExternalId": "<string>",
"documentation": "<string>",
"type": "global",
"extractorExternalId": "<string>"
}
]
}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.
List of solutions.
List of source systems
Show child attributes
Was this page helpful?