⌘K
Amy Egan Sorry to hear you had some unexpected high usage, @pabloost. Do you have a support case open? The community isn't able to issue refunds. For security reasons, that kind of thing is limited to the support team. If you don't have a case yet, please open one at vercel.com/help so the support team can assist
Pablo Hey! Thanks for your help. Unfortunately, I can´t as an agents responds automatically without the option to talk with support team :-(
Amy Egan It should let you open a case if you ask to talk to a person. Can you try again and let me know what it tells you if it doesn't help you open a case?
system 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 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Omediae Following up on this unresolved question. Could someone from the Firewall team clarify: 1. What supported operation creates the first unpublished firewall draft without activating it? The REST reference and CLI use different endpoints. 2. Does PUT /config stage or immediately activate configuration? 3. What JSON shape supports a fixed-window SDK rule with an over-limit Log action and API-controlled keys? 4. Is environment=preview supported for SDK rate-limit requests? We understand Hobby’s one-rate-limit-rule allowance and three-custom-rule ceiling. We’re seeking a safe, supported single-rule test—not additional quota. The test remains protected, synthetic-only and disabled pending clarification. Please route this to the Firewall team if necessary.
Hercules 8202 Yeah this is would be really nice to have
naaiyy +1 on this !
Ed Hollinghurst Bumping this after three months with no response from the Vercel team. I've re-checked the current state today (30 Oct 2026): - The Web Analytics API docs still list `requestPath`, `route`, `country`, `referrerHostname`, `deviceType`, `browserName`, UTM fields and `flags` as the supported dimensions. `requestHostname` isn't among them. - The same list is enumerated in the OpenAPI spec and in the Vercel MCP tool schemas for `visits/count` and `visits/aggregate`. - The response schema for both aggregate endpoints already includes a `requestHostname` field, so the data is clearly stored and queryable. It just can't be used in `filter` or `by`. - The dashboard has supported filtering by hostname since April 2024, and the dashboard's own query API accepts the filter. So the gap is purely in the public API's allow-list of filter subjects, not in the data. The concrete request: 1. Accept `requestHostname` as a filter subject on `visits/count`, `visits/aggregate`, `events/count` and `events/aggregate`, e.g. `requestHostname eq 'tenant.example.com'`. 2. Accept `requestHostname` as a `by` dimension on the two aggregate endpoints, so one call can return pageviews and visitors per hostname. For context on why this matters: we have a multi-tenant app where every customer gets their own subdomain or custom domain on a single Vercel project. We want to show each customer their own visitor stats inside our product. Without a hostname filter the API can only give us project-wide totals, which are useless to an individual customer. Other people in this thread have the same multi-tenant setup. Could someone from the Web Analytics team confirm whether this is on the roadmap, or whether there's a reason it was left out of the public API?
