Skip to main content
The asset-centric OData service lets you access CDF resources such as assets, time series, events, files, sequences, and RAW data via an OData API. The asset-centric OData service accepts URLs with the following schema:
Where:
  • {cluster}: the name of the CDF cluster, e.g., westeurope-1.
  • {apiVersion}: the version of the OData service API (latest is v1).
  • {project}: the name of the CDF project, e.g., publicdata.
If you point the OData client to the correct asset-centric OData URL and authenticate, the server returns a table with all asset-centric types currently supported by the OData service in addition to supported OData functions.

Filtering asset-centric resource types

The asset-centric OData service can push filters down to CDF. This improves performance by ensuring that filtering happens on the server side, reducing the amount of data transmitted to the client.

Filtering options

  • Pushdown: Filter functions that are pushed down to the CDF backend. This is the most efficient filtering.
  • Local: Filtering done by the OData service before returning the result to the client. Less efficient than pushdown.
  • Client-side: Filtering done by the client after data is retrieved. Least efficient.

Definitions

  • FilterFunctions: Contains, StartsWith, and EndsWith.
  • Comparison: <, <=, >, >=, and =.
  • Search: uses the search API and may require additional local filtering.
Search returns a limited number of rows, and you may not receive all matching data in CDF.

Assets

Time series

Data point

Events

Files

Sequences

Supported via the Sequences(id) syntax.

CDF RAW databases

CDF RAW tables

CDF RAW rows

Supported OData functions

AssetsRoots

Fetch the root assets for a CDF project.

AssetsSearch

Search assets in a CDF project.

EventsSearch

Search events in a CDF project.

TimeseriesAggregate

Aggregate data points from multiple time series.

TimeseriesSearch

Search time series in a CDF project.
Last modified on December 9, 2025