Skip to main content
err:user:bad_request:per_key_breakout_too_large
Example

​
What happened?

portal.getVerifications returns one timeseries per key the end user has verifications for, so a client can render a per-key table and an account-wide chart from a single call. At most 150 keys come back in one response. That bound keeps a single portal session from pulling an unbounded result over the ClickHouse connection every workspace shares. More than 150 of the end user’s keys had verifications in the window you asked for, so the request was rejected rather than answered with a partial list. A truncated breakout is indistinguishable from the omitted keys having had no traffic at all, which would quietly understate the account’s usage. The limit counts keys with traffic inside the requested window, not keys on the account. An identity with thousands of keys stays well under it over a short window if only a few were used. The detail field carries the exact limit that was applied.

​
How to fix it

​
1. Request a shorter window

Because the count is scoped to the window, narrowing it is usually enough:

​
2. Request a single key

When you need a long window for one key, pass keyId and the response carries just that series:
Page through the keys you care about with one call each rather than asking for every key at once.
Last modified on September 17, 2026