Schedule custom reports for your driver failure details
Use these asynchronous methods to access reporting data for your Win10/ Win 8.x driver errors and OEM hardware errors. You can define reporting templates based on your needs, set a schedule and you will have data delivered to you at regular intervals.
- These methods can only be used by developer accounts that belong to the Windows Hardware Dev Center program.
- These methods can be used in place of the existing methods to determine Windows 10 driver errors, Windows 7 and Windows 8.x driver errors (for IHVs), and hardware errors (for OEMs).
- These methods expose a rich set of new dimensions and supports look back for as much as 90 days in the past.
- The API documentation is also available in Swagger
You must complete the requirements outlined in Enable secure data sharing.
To use this method, you need to first do the following:
- If you have not done so already, complete all the prerequisites for the Microsoft Store analytics API, including obtaining an Azure AD access token to use in the request header for this method. Note that after you obtain an access token, you have 60 minutes to use it before it expires. After the token expires, you can obtain a new one.
For more information, see Access analytics data using Microsoft Store services
As a reminder, the Windows Analytics Agreement states: “You must not store Personal Information for longer than thirty (30) days. Following such 30-day period, you will immediately destroy the Personal Information.”
Workflow to schedule custom reports for driver failure
The following diagram explains the API call pattern to create a new report template, schedule the custom report and retrieve failure data.
The Client Application defines the report schema in JSON format and call the Create Report Template API.
On success, the Create New Report Template API returns the TemplateId.
The client application calls the Schedule Custom Report API using the TemplateId along with the report start date, Repeat Interval and Recurrence.
The client application could also send a callback URL to be notified once data for the scheduled report is ready.
On Success, the Schedule Custom Report API returns the ReportID.
The callback URL gets a notification once the data is ready for download on a regular basis.
The client application then uses the Get Report Data API using the ReportID to query the status of the report with the Report ID and date range.
On success, the report download link is returned and the application can initiate download of the data.
The report data contains the CabIdHash that can be used as input to the Cab Download API, to download the cab files.
The Cab Download API returns the cab download link that can be used to download the cab files.
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.