Custom Reporting API
The Custom Reporting API offers a powerful tool to pull complex reports from Ooyala Pulse, within limits. The Custom Reporting API allows you to generate reports as you need them, without having pre-existing report definitions, unlike the Insight Reporting API. This means that:
- You create report definitions from scratch for each new report, stating the metrics, dimensions and filters you want.
- Reports can be generated for unaggregated data.
- Reports may be slower to generate, because data needs to be aggregated each time you generate a new report.
- Base URL: https://api.videoplaza.com/v2/reports
- Requests: GET and POST requests are used. You pass parameters by using common REST parameters like PATH and QUERY, as well as HTTP HEADERS. The body of the requests should be provided in JSON format and encoded using UTF-8.
- Responses: All responses contain an HTTP status code in the header and the body is in JSON format, except for fetching the generated report, where the response is in CSV format.
- Swagger documentation: https://api.videoplaza.com/v1/swagger
- Related user documentation:
- Reports return maximum 100000 rows.
- You can store at most 200 reports. If another report is created after the allocation is filled, then the report with the oldest creation date is removed.
- You can define maximum eight grouping dimensions for a report.
- You can run maximum two reports at the same time, which means that if there are still two reports waiting to complete in Custom Reporting, you cannot create another report to run in Custom Reporting.
- The query for a report runs for maximum 5 hours. Queries that take longer are cancelled, and the report's status is set to 'Failed'.
- Data for Custom Reporting is only available for the past 25 months. Reports where at least a part of the selected time span falls outside the data retention period, fail to run.
- Only the described dimensions, metrics, and filters in this document set are available in Custom Reporting.
- Revenue metrics are visible to all users of your Pulse account when using Custom Reporting, even if a particular user cannot see revenue metrics in the Pulse User Interface.