Judge.me · Rate Limits

Judge Me Rate Limits

Judge.me applies per-shop throttling on its REST API to protect the platform, but does not publish specific request-per-minute or per-day numbers in its public API documentation. Clients should expect HTTP 429 responses under heavy load - particularly when paginating large review exports - and should page conservatively and back off when throttled. Specific limit values are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Reviews, E-commerce, Shopify, Ratings, and Social Proof.

2 Limits Throttle: 429
ReviewsE-commerceShopifyRatingsSocial ProofRate LimitingQuotasThrottling

Limits

Requests Per Shop shop
requests
see provider documentation
Per-shop_domain throttling; specific values not published.
Review Export Pagination shop
requests
see provider documentation
Large bulk review exports should be paginated conservatively to avoid throttling.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.
Token Separation
Use the public token only for GET widget calls and the private token server-side; do not expose the private token in client code.

Sources