Apply API request throttling | Pixie CRM Help Centre
Canonical: https://pixiecrm.com/help-centre/apply-api-request-throttling
Publisher: Pixie Technologies LLC

Core CRM security hardening
Apply API request throttling

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains rate controls protecting authenticated and token-based API traffic.

Audience: Administrators and deployment engineers; Permission: Core release / deployment authority; 

Where to goAutomatic core protection — no separate staff menu route

What this guide helps you do

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.

Follow these steps

- Use the supported Pixie CRM release or workflow that produces this security control.

- Check the expected protection through an authorised test.

- Record the result in the deployment or security audit evidence.

Fields and options

- API token identity

- Request rate

- Usage metadata

Rules and limits

- 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.

Check it worked

- 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

Apply client login throttling (https://pixiecrm.com/help-centre/apply-client-login-throttling)Apply two-factor authentication throttling (https://pixiecrm.com/help-centre/apply-two-factor-authentication-throttling)Apply staff login throttling (https://pixiecrm.com/help-centre/apply-staff-login-throttling)Use secure HttpOnly and SameSite cookie defaults (https://pixiecrm.com/help-centre/use-secure-httponly-and-samesite-cookie-defaults)

Connected discovery, service and API guides

Gateway portal profile rate limit (https://pixiecrm.com/help-centre/proplix-secure-api-gateway-portal-profiles-tokens-rate)Public Service Journey rate limiting (https://pixiecrm.com/help-centre/service-journeys-types-intake-public-rate-limit)