Subbly · Rate Limits

Subbly Rate Limits

Subbly does not publish numeric rate limits for its developer surface. The storefront developer tools - SubblyCart.js and the Subbly.js SDK - call Subbly's REST backend authenticated with a shop apiKey (and optional customer access token), but Subbly documents neither the endpoint paths nor any per-key request-rate or quota limits. The public Orders API (3PL integration) is access-gated and its limits, if any, would be shared by Subbly when the documentation is provided on request. Webhook delivery volume tracks the shop's order and subscription activity rather than a published cap.

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

It captures 3 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 Subscriptions, Ecommerce, SDK, Rate Limiting, and Quotas.

3 Limits Throttle: 429
SubscriptionsEcommerceSDKRate LimitingQuotas

Limits

Storefront SDK / Cart Requests apiKey
requests
not published
No fixed numeric request-rate limit is documented for SubblyCart.js or the Subbly.js SDK backend.
Orders API (3PL) account
requests
not published
Access-gated Orders API; any limits would be shared by Subbly with the on-request documentation.
Webhook Delivery account
events
not published
Outbound webhook volume follows the shop's order/subscription events; no published cap.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.
Client-Side Key Exposure
The SubblyCart.js / SDK apiKey is a public storefront key configured client-side; do not embed secret server credentials in the browser.

Sources