Storable · Rate Limits

Storable Rate Limits

Storable's public storEDGE v1 API reference does not publish a numeric per-minute or per-day request-rate limit. It does document collection-level pagination: any endpoint returning a collection accepts page and per_page query parameters, and responses are limited to 100 items by default unless per_page is set. Every response body carries a meta hash with status_code, status_message, error_code, and request_id, which is the mechanism for surfacing throttling or authorization errors rather than a documented numeric quota. No rate-limit information is published for SiteLink's legacy SOAP API, whose reference document itself sits behind an NDA.

Storable Rate Limits is the machine-readable rate-limit profile for Storable on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring items and requests.

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 Self Storage, Property Management, storEDGE, Rate Limiting, and Pagination.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Self StorageProperty ManagementstorEDGERate LimitingPagination

Limits

Collection Page Size request
items
100 default, configurable via per_page
Applies to any storEDGE endpoint that returns a collection (tenants, units, leads, ledgers, etc.).
API Request Rate account
requests
not published
No fixed numeric request-rate limit is documented for the storEDGE v1 API.
SiteLink Legacy API account
requests
not published
SiteLink's SOAP API reference is NDA-gated; no public rate-limit information exists.

Policies

Facility Scoping
Every storEDGE request is scoped to a single facility_id (or company_id at the corporate level) baked into the URL path, which is the primary access boundary rather than a throttling mechanism.
Required Headers
Storable's docs "highly recommend" sending Content-Type and Accept headers set to application/json on every call, noting some calls may not succeed without them.
Backoff Recommendation
As with most REST APIs, clients should implement retry with backoff on 5xx and any throttling responses, honoring Retry-After if present, though Storable does not explicitly document this header.

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/storable-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.