PushPress · Rate Limits

Pushpress Rate Limits

PushPress does not publish fixed numeric rate limits for the Platform API in its public reference as of the review date. The official SDK ships automatic retry behavior with exponential backoff on 5XX responses and connection errors, which implies clients should be resilient to transient throttling and server errors. Treat HTTP 429 as the throttle signal, honor any Retry-After header, and back off exponentially with jitter.

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

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

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

Tagged areas include Fitness, Gym Management, SaaS, Rate Limiting, and Quotas.

2 Limits Throttle: 429
FitnessGym ManagementSaaSRate LimitingQuotas

Limits

Platform API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Platform API.
Messaging Sends account
messages
not published
Email / SMS / push / notification send volume is subject to platform and downstream carrier limits, not a published API cap.

Policies

Retry with Backoff
The official SDK retries on 5XX responses and connection errors using an exponential backoff strategy (initial 500ms, up to 60s, ~1.5x exponent). Clients should implement the same and honor Retry-After on 429 responses.
Idempotency
Prefer read-then-write patterns and treat webhook deliveries as at-least-once; deduplicate on event id where retries may occur.

Sources