This contract is currently in the Proof-of-concept stage and is still subject to change
Introduction
To expose Reporting services to our system, we need an API to be exposed for the MediaHaven installation. When creating new Module Plugins having of the following Plugin Category:
Business Intelligence
then MediaHaven will connect to this plugin using REST API calls, which Our product can integrate with a variety of business intelligence (commonly called BI) tools. By configuring new Module Plugins with the category “Business Intelligence”, MediaHaven will produce a list of reports by combining all reports across all plugins of this category.
Methods
A connector of the category “Business Intelligence” must implement the following methods depending on the category.
...
GET /reports
...
colour | Blue |
---|---|
title | Business Intelligence |
Return Returns a list of embeddable report URLs, they MUST be embeddable. Meaning . This means those URLs can be safely embed embedded into a 3rd party website (=MediaHaven FrontEnd in this case)
Example and reference, please see metabase’s static embedding, which utilize JWT signing to defend against 3rd party website tamper with the embedded URL’s path parameter
Optional parameters
...
, specifically the MediaHaven frontend. If the BI tool wants to protect itself against tampering of the URL by the end-user (e.g. changing a parameter), then the connector should produce a signed URL which is inherently tamper-proof.
Optional parameters
Depending on the application and the authorizations of the user
Parameter | Usage | Example |
---|---|---|
collection | When the installation contains multiple applications, then the collection parameter specifies which application it concerns | Seriesregister, e-Depot |
|
filter.* parameters are parameters that should be handled by the reports as fixed filter parameters.
...
When the user has no access across all organisations, then these parameters restrict the results that should be displayed in the report to this organisation. Specifically, if the user has the function | The organisation of the user |
Expected headers
Code Block |
---|
x-api-key: <reporting engine api key> |
Output
Expand | |||||||||
---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
GET /reports/:id
Returns a specific report with the ID
Expected headers
Code Block |
---|
x-api-key: <reporting engine api key> |
Output
...
Expand | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||
|