BlueCart · Rate Limits

Bluecart Rate Limits

The public BlueCart API documentation at docs.bluecart.com does not publish explicit per-second, per-minute, or per-key request-rate numbers. The API is fronted by AWS API Gateway (AWS Signature Version 4 against the execute-api service in us-east-1), so account-level throttling and burst limits are enforced at the API Gateway tier and would surface as HTTP 429 responses; the exact values are not documented publicly and would be governed by the account's API Gateway usage plan. Collection endpoints enforce a fixed page size of 25 items via next-token cursor pagination, and the API operates on a single object per request (no bulk updates), which bounds per-request work. All numeric limits below are unconfirmed against published BlueCart docs.

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

It captures 3 rate-limit definitions, measuring requests_per_second and varies.

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

Tagged areas include Rate Limiting, Wholesale, Procurement, and eCommerce.

3 Limits Throttle: 429 Quota: 429
Rate LimitingWholesaleProcurementeCommerce

Limits

API Gateway request throttling account
requests_per_second
governed by the account AWS API Gateway usage plan; not published in BlueCart docs
BlueCart fronts the API with AWS API Gateway. Steady-state rate and burst are configured per usage plan and not documented publicly.
Collection page size account
varies
25 items per page (fixed; defined in the internal pagination configuration for the resource)
Search/list endpoints return 25 records per page and require the returned nextToken to fetch subsequent pages.
Objects per request account
varies
1 object per request (no bulk updates)
The API works on only one object per request.

Policies

Cursor pagination
Use the nextToken returned in each collection response to retrieve the next page. When no nextToken is returned, the final page has been reached.
AWS SigV4 signing
Every request must be signed with AWS Signature Version 4 using the Access Key ID and Secret Access Key, with the BlueCart API Key supplied in the x-api-key header. Unsigned or mis-signed requests are rejected.
Retry on throttling
On HTTP 429 responses, back off and retry with exponential backoff, as is standard for AWS API Gateway-fronted APIs.

Sources