Bugfix: Update for requests to the Web Analytics API with missing scope
Currently, requests to theWeb Analytics APIthat do not have the correct scope return an HTTP 200 response with an empty response body, instead of returning an error. This can result in confusion that data doesn't exist when the actual issue is with the scope of the access token used for the API request.
What's changing?
Beginning on January 4th, 2023, we'll return the correct HTTP 403 response indicating the missing scope. Please note that no changes are being made to the data, or which accounts or apps will have access to the data from this API.
If you're currently receiving HTTP 200 responses with an empty response body, you should check your app settings oraccess tokensto make sure that the `business-intelligence` scope is included.
No one has replied to this post quite yet. Check back soon to see if someone has a solution, or submit your own reply if you know how to help! Karma is real.