Airbase · Rate Limits

Airbase Rate Limits

Airbase does not publish public numeric rate limits for its developer API. The API reference sits behind an account-gated developer portal (developer.airbase.io), so any per-account or per-endpoint request limits are governed inside the customer's Airbase/Paylocity tenant and are not documented in the open. Standard REST client hygiene - exponential backoff with jitter, honoring Retry-After on HTTP 429, and idempotent retries - should be assumed.

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

It captures 2 rate-limit definitions, measuring requests and events.

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

Tagged areas include Spend Management, Paylocity, Rate Limiting, Quotas, and Gated API.

2 Limits Throttle: 429
Spend ManagementPaylocityRate LimitingQuotasGated API

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented publicly; governed inside the account-gated portal.
Webhook Delivery subscription
events
not published
Outbound webhook delivery (e.g. purchase request approved / milestone events); retry/delivery semantics not publicly documented.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Account-Gated Governance
Because access is provisioned per Airbase/Paylocity tenant, effective limits are enforced and communicated within the account rather than via public documentation.

Sources