Request access to read-only Web Analytics API permissions beta

Hi Vercel team,

Could you help enable the Sign in with Vercel API-permissions beta for our Anna Health team, or point us to the team handling access requests?

We need unattended aggregate Web Analytics reporting for one landing project. The intended Vercel App grant is Web Analytics: Read Only and Projects: Read Only, restricted to that single project. We want to keep access narrow rather than use a broad account token.

What we observed:

We created an App, but its Permissions editor exposes only OpenID identity scopes. With the enabled-only filter removed, searching for Web Analytics returns no matching permission.
A private integration restricted to the project with Installation Read and Project Read can read the selected project's metadata (HTTP 200), and access outside that project is denied.
The same integration token gets HTTP 404 / not_found from GET /v1/query/web-analytics/visits/aggregate. The identical request succeeds through our existing operator access.

The Scopes and Permissions documentation lists the two project read permissions as private-beta capabilities. Vercel's support intake directed this beta-access request to Community and did not open a case.

Can Vercel staff enable those exact read-only permissions, or confirm a supported equivalent limited to one project? We can provide team and App identifiers privately to verified Vercel staff if required.

Thank you.

There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.