Week in review
This week improves the developer experience when working with the reporting API’s access control responses.Updates
- Clearer reporting API error responses — The
/reports and /financial-reports endpoints now return detailed error examples in 403 Forbidden responses. If your integration handles authorization errors programmatically, the response body now includes a structured FORBIDDEN error with a descriptive message, making it easier to surface the right feedback to your users. Learn more
Last modified on April 16, 2026