Limits

Four limits apply to every credential. Two are settings; two are fixed by the system.

Why two are fixed

• The body size has to match the web server in front of the application. A larger figure here would be refused before BrizoConsol ever saw the request.
• One request at a time per organisation exists because two requests for the same month at once would count that month twice. It is not enforced yet, so until then it is the rule a caller should follow rather than one the API refuses.

Changing a group’s limits

System administration → API limits, visible to the system administrator only.

Each group on Pro or Premium is listed with its own values and whether it uses the defaults. A field left empty means “use the default”; filling one changes that limit for that group alone. The change is written to the System Audit Trail, with the value before and after.

What the caller is told

The schema endpoint states the limit the caller will be measured against:

GET /api/v1/schemas/trial_balance

{
  "...": "...",
  "record_limit": 250
}

That figure is the group's own when the call carries a live token, and the default when it does not - a caller is never told one number and refused against another. A request over the limit is refused with 422, and a caller over its requests-per-minute limit gets 429.