The Insights API is a tool for aggregating digital twin data from multiple sources into one unified format and place. With the Insights API, consuming your data through business intelligence applications such as Power BI or your own custom-built application is dramatically simplified.
The Insights story begins with Mapping. Mapping is a configuration process where all desired data sources are identified. These Mappings also will help describe what data is desired from each data source and how to structure it for Insights. The Mapping process will be unique for each type of data source. For example, a Mapping for data from an iModel may not look the same as a Mapping for data from Validation, but ultimately all that data needs to arrive at one place and that is what Mapping orchestrates for you.
A Report represents a collection of data. The way the Insights API views a Report is as a collection of Mappings. With the Insights API, you will assign one or more Mappings to a Report to be consumed by some application such as Power BI as a single data source.
More often than not, some preprocessing will be required before data defined in a Mapping is actually available to be consumed as a Report. Endpoints are provided in the Insights API to trigger the data extraction process. Depending on the data source this may be a one-time action, required for data syncs, or not required at all. See data source specific documentation to find out more.
Accessing the resulting data is done using a set of OData v4 endpoints. Any application that can use the OData protocol such as Power BI will automatically understand how to fetch your Report data. Access to data can either follow the standard Bearer Token authorization shared with all other Insights APIs, or use Basic Authentication with the credentials and keys provided via the API Keys dashboard.
Described for an iModel data source. Some variation may exist for other data sources.
- Create an empty iModel Mapping.
- Create one or more Groups under that Mapping. A Group is a collection of iModel elements defined by a query.
- Create one or more Group Properties for each Group. These are the properties to be extracted from the iModel elements and how they should be identified in your Report.
- Create a new Report.
- Assign the Mapping created to the new Report (Report Mappings).
- Run the iModel Extraction.
- Ensure the Extraction has completed.
- Create a new Api Key through the API Keys user interface that has access to the new Report.
- Connect an OData v4 compliant application to the Report using the generated ApiKey.