veeva · Rate Limits

Veeva Rate Limits

Veeva Vault enforces tenant-scoped API rate limiting on the Authentication API and other surfaces. The published documentation states limits are based on user name + domain name, but does not publish global per-second / per-minute numeric ceilings; the actual burst limit and throttling delay are exposed to administrators via response headers and the in-product API Usage Logs (Admin > Settings > Logs > API Usage Logs).

2 Limits
Life SciencesSaaSRate Limiting

Limits

Authentication API rate limit user/domain
varies
tenant-specific; check Auth API rate-limit response headers or API Usage Logs
Veeva docs confirm a limit exists keyed on the user name + domain name in the API call but do not publish a numeric ceiling.
General Vault API rate limits tenant
varies
see API Usage Logs in the Vault tenant
Burst behavior and throttling delays are tenant-configured and surfaced through response headers.

Policies

Inspect response headers
Clients should read Auth API rate-limit response headers to determine remaining capacity and any throttling delay applied to the current call.
Consult API Usage Logs
Vault administrators can review actual rate-limit behavior and throttling events under Admin > Settings > Logs > API Usage Logs to determine the tenant's effective limits.

Sources