SPOD · Rate Limits

Spod Rate Limits

The SPOD (Spreadconnect) REST API applies a per-integration request rate limit of approximately 60 requests per minute. Requests beyond the limit are rejected with an HTTP 429 response and should be retried with backoff. Webhook notifications from SPOD to your endpoint follow an at-least-once delivery model with an increasing retry delay when acknowledgements are missed, rather than a fixed client-side rate.

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

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

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

Tagged areas include Print on Demand, POD, Fulfillment, Rate Limiting, and Quotas.

2 Limits Throttle: 429
Print on DemandPODFulfillmentRate LimitingQuotas

Limits

API Requests integration
requests
~60 per minute
Per-integration request rate limit; exceeding it returns HTTP 429.
Webhook Notification Acknowledgement subscription
seconds
8 second response window
Notifications must be acknowledged within 8 seconds with a 202 and payload [accepted], or they are retried.

Policies

Backoff and Retry
On HTTP 429, clients should back off and retry with increasing delay. Honor any Retry-After guidance.
At-Least-Once Delivery
Webhook notifications are guaranteed to be delivered at least once; the retry delay increases over time to avoid flooding the receiver.
Idempotent Acknowledgement
Because notifications can be delivered more than once, receivers should handle duplicate events idempotently.

Sources