Argyle · Rate Limits

Argyle Financial Rate Limits

Rate limit definitions for the Argyle REST API. Argyle publishes a single request-rate ceiling of 50 requests per second across the integration; consumer-permissioned data sets are additionally bounded by source-platform refresh windows and ongoing-refresh schedules.

Argyle Financial Rate Limits is the machine-readable rate-limit profile for Argyle on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, across the sandbox, production, and enterprise tiers, measuring requests_per_second and refresh_per_day.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Employment Data, Income Verification, Payroll, Rate Limiting, and Quotas.

4 Limits Throttle: 429 Quota: 429
Employment DataIncome VerificationPayrollRate LimitingQuotasThrottling

Limits

Sandbox Default api-key
requests_per_second · second
50
Production Default api-key
requests_per_second · second
50
Enterprise Negotiated Limit contract
requests_per_second · second
-1
Ongoing Refresh Cadence account
refresh_per_day · day
1

Policies

429 Throttling
Exceeding the documented 50 RPS ceiling returns HTTP 429. Clients should implement exponential backoff with jitter and honor the Retry-After response header when present.
Webhook Backpressure
Failed webhook deliveries are retried with backoff. Endpoints that consistently return 5xx may be disabled — subscribers must monitor delivery state through Argyle Console.
Ongoing Refresh Windows
Source payroll, gig, and banking platforms enforce their own refresh windows. Even on enterprise tiers, data freshness is bounded by the source platform; Argyle does not bypass these limits.
Sandbox Isolation
Sandbox traffic is metered separately and never consumes production capacity. Production keys must not be used against the sandbox host.