SmartMoving · Rate Limits

Smartmoving Rate Limits

SmartMoving governs the Open API primarily through a monthly call quota tied to the API tier rather than a published per-second request rate. The Basic tier allows 20,000 calls per month and pauses access once the cap is reached until the next billing cycle. The Premium tier allows 125,000 calls per month; when exhausted, Premium customers can buy additional call packs ($149 each, up to five at a time) or enable automatic pack purchases that trigger at 90% usage. The Open API is fronted by Azure API Management, which enforces the quota and standard gateway throttling. The free Lead API is a separate intake endpoint and is not counted against these Open API quotas.

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

It captures 5 rate-limit definitions, measuring requests.

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

Tagged areas include Moving Software, CRM, API, Rate Limiting, and Quotas.

5 Limits Throttle: 429
Moving SoftwareCRMAPIRate LimitingQuotas

Limits

Basic Monthly Quota account
requests
20000 per month
Read-only Basic tier. Access pauses when reached and resets the next cycle.
Premium Monthly Quota account
requests
125000 per month
Read/write Premium tier. Overage handled via purchasable call packs.
Premium Overage Pack account
requests
purchasable (up to 5 packs at a time)
$149 per additional call pack; optional auto-purchase triggers at 90% usage.
Gateway Throttling account
requests
not published
Azure API Management may throttle bursts with HTTP 429 independent of the monthly quota.
Lead API provider-key
requests
not published
Free lead-intake endpoint, separate from Open API quotas.

Policies

Quota Reset
Basic-tier access is restored at the start of the next monthly billing cycle after the cap is hit.
Overage Packs
Premium accounts extend capacity by purchasing call packs, up to five at a time, with optional automatic purchase at 90% usage.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses from the gateway.

Sources