Very Good Security · Rate Limits

Vgs Rate Limits

VGS does not publish a single fixed numeric rate-limit table for the Vault and Accounts APIs. Throughput is governed by plan, vault tier, and the consumption-based interaction model, and high-throughput needs are arranged with VGS. Clients should expect throttling under burst load and handle 429 responses with backoff. Specific per-endpoint limits are not reconciled in this artifact.

Vgs Rate Limits is the machine-readable rate-limit profile for Very Good Security on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests and interactions.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Security, Tokenization, Data Privacy, PCI Compliance, and Vault.

4 Limits Throttle: 429
SecurityTokenizationData PrivacyPCI ComplianceVaultRate LimitingQuotasThrottling

Limits

Vault API Requests vault
requests
see provider documentation
Tokenization (alias) request throughput governed by plan and vault tier.
Vault Interactions account
interactions
plan-dependent
Billed consumption unit; token creation and data exchange counts scale with package.
Accounts API Requests organization
requests
see provider documentation
Control-plane management calls for organizations, vaults, and routes.
Reveal Operations vault
requests
disabled by default
Bulk and single reveal endpoints are disabled by default and enabled by VGS on request.

Policies

Tiered Limits
Throughput and interaction allowances scale with Starter, Growth, and Enterprise packages.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources