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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-11.
Written by API Evangelist on 2026-07-11 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/spod-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.