I am implementing an Integration with Microsoft O365 Reporting API and wanted some support regarding the Microsoft Message Trace API, specifically concerning the following aspects:

Rate Limits: Can someone please provide detailed information on the current rate limits applicable to the Message Trace API? Understanding these limits is crucial for optimizing our API usage and ensuring we stay within the allowed thresholds.Pagination Approach: I would appreciate guidance on the recommended pagination approach when querying the API. Specifically, we’d like to know how to handle large datasets efficiently and whether there are best practices or built-in mechanisms for managing pagination in API responses. I am able to hit the API and hence, getting some response but unable to retrieve the Next page or any similar parameter which will allow me navigate to the next page.Generating Additional Data for Reporting: Lastly, I am exploring ways to generate more comprehensive data through the API for reporting purposes. Could anyone advise on any available options or techniques to retrieve a broader range of data points or more detailed logs from the API?Retention Policy: would like to know about the Retention policy of this API. Let me know if it varies from account level permissions/access?

Someone’s assistance is greatly appreciated, as it will help me ensure that the integration with Message Trace API is both efficient and compliant with best practices.
Reference links:

https://learn.microsoft.com/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984335%28v%3doffice.15%29 
API Link:
https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA%20options] 

Thank you in advance for your support.

​I am implementing an Integration with Microsoft O365 Reporting API and wanted some support regarding the Microsoft Message Trace API, specifically concerning the following aspects:Rate Limits: Can someone please provide detailed information on the current rate limits applicable to the Message Trace API? Understanding these limits is crucial for optimizing our API usage and ensuring we stay within the allowed thresholds.Pagination Approach: I would appreciate guidance on the recommended pagination approach when querying the API. Specifically, we’d like to know how to handle large datasets efficiently and whether there are best practices or built-in mechanisms for managing pagination in API responses. I am able to hit the API and hence, getting some response but unable to retrieve the Next page or any similar parameter which will allow me navigate to the next page.Generating Additional Data for Reporting: Lastly, I am exploring ways to generate more comprehensive data through the API for reporting purposes. Could anyone advise on any available options or techniques to retrieve a broader range of data points or more detailed logs from the API?Retention Policy: would like to know about the Retention policy of this API. Let me know if it varies from account level permissions/access?Someone’s assistance is greatly appreciated, as it will help me ensure that the integration with Message Trace API is both efficient and compliant with best practices.Reference links:https://learn.microsoft.com/en-us/previous-versions/office/developer/o365-enterprise-developers/jj984335%28v%3doffice.15%29 API Link:https://reports.office365.com/ecp/reportingwebservice/reporting.svc/MessageTrace[?ODATA%20options] Thank you in advance for your support.  Read More

​