Apicbase · Rate Limits

Apicbase Rate Limits

The Apicbase REST API is a subscription-included interface secured with OAuth 2.0 bearer tokens. The public developer documentation does not publish specific numeric request rate limits, quotas, or throttling thresholds. List endpoints are paginated (via a page parameter), which bounds response size. Specific per-account or per-endpoint rate-limit values are not reconciled in this artifact.

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

It captures 3 rate-limit definitions, measuring requests, records_per_page, and seconds.

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

Tagged areas include Food and Beverage, Restaurant, Back of House, Inventory, and Procurement.

3 Limits Throttle: 429
Food and BeverageRestaurantBack of HouseInventoryProcurementRecipesRate LimitingQuotasThrottling

Limits

Request Rate account
requests
see provider documentation
No public numeric request rate limit is documented; verify on reconciliation.
Pagination endpoint
records_per_page
see provider documentation
List endpoints are paginated via the page query parameter.
Access Token Lifetime token
seconds
604800
OAuth 2.0 access tokens expire after 7 days; refresh tokens issue new access tokens.

Policies

OAuth 2.0 Bearer Authentication
All requests must use HTTPS and present a valid bearer access token in the Authorization header.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.

Sources