Apply API request throttling

Understand rate controls protecting authenticated and token-based API traffic.

What this guide covers

Understand rate controls protecting authenticated and token-based API traffic. The workflow below follows the supported application or module flow and does not invent a menu or bypass validation.

Exact step-by-step process

1. Use the supported Britixo CRM release or workflow that produces this security control.
2. Verify the expected protection through an authorised test.
3. Record the result in the deployment or security audit evidence.

Fields, choices and supported possibilities

• API token identity
• Request rate
• Usage metadata

Code-backed validations and workflow rules

• API clients must respect rate-limit responses and implement backoff.
• Throttling does not authorise an otherwise forbidden API operation.
• Tokens must not be shared across unrelated systems merely to avoid rate controls.

Expected result and verification

• The protection is active without weakening another security control.

Security, audit and troubleshooting checks

• Use the exact authorised account, role and record before saving or sending.
• Verify the saved status and downstream record; a browser success message alone is not sufficient evidence.
• Never expose passwords, API keys, access tokens, protected attachments or raw server paths in support tickets.
• Do not edit module or core database records directly to bypass validation, permissions, migrations or state rules.

Related guides

Connected discovery, service and API guides