Sandbox ceilings
Every Sandbox organization gets these numbers, whatever plan it holds in Live. They are not settings: nobody can raise one for you.
Every refusal is the error
SANDBOX_LIMIT_REACHED. details.limit names the ceiling and
details.value states its number. The 429 refusals carry a Retry-After header in
seconds. The 403 refusals do not clear by waiting, so repeating the request cannot
succeed until you free something.
Where a Reset frees the ceiling, details.reset names the route and the console path:
Settings, Sandbox, Reset the sandbox. See Errors.
A resend of a record the organization already holds is never refused for records,
bytes or deployment: it stores nothing new.
The Sandbox has no monthly quota and no overage, and is never billed.
Live limits
Live limits come from your plan: the request rate, the number of API keys and agents, and the monthly usage allowances. A request over the rate limit answers 429RATE_LIMIT_EXCEEDED. A request over a monthly allowance that your plan caps answers 429
QUOTA_EXCEEDED. Ask the Sanning team for the numbers on your plan.
Live has no purge and no Reset, so the records, bytes and deployment ceilings
exist only in the Sandbox.