Feature Request: Individualized Pagination Endpoint for Time Series Datapoints API

Hi,

It would be great to have the creation of an endpoint based on the one below:
https://api-docs.cognite.com/20230101/tag/Time-series/operation/getMultiTimeSeriesDatapoints

Currently, this endpoint allows requesting multiple items in a single call and returns the next page individually for each requested item.

For Celonis’ REST extractor, this pagination model creates a limitation, as the platform works better with individual pagination, where each response contains only one component and a single pagination continuation token.

Today, to enable this extraction, a Python-based workaround is being used within the environment, since the current model is not compatible with the standard extractor.

We would like to check if it is possible to make the endpoint available in a more individualized format, with one time series per response, or if there is already an alternative endpoint that supports this scenario. This would greatly help improve the standardization and stability of the integration.

Sharing the user’s assessment regarding the available data extraction methods:

Extraction Builder

This solution, offered by Celonis, works very well for REST APIs. However, for the current endpoint structure, pagination is not supported. To solve this issue, it would be enough to update or create a new endpoint that returns only one result per response instead of a nested list structure.

SDK

The SDK offers a flexible solution but carries higher implementation risk. It would require using an existing middleware layer to orchestrate the extractions, which is currently considered unfeasible due to resource constraints, access dependencies, and a longer development timeline compared to other alternatives.