ServiceM8 · Rate Limits

Servicem8 Rate Limits

ServiceM8 applies API throttling on a per-application and per-account basis. The documented limits are 180 requests per minute and 20,000 requests per day. Exceeding either limit returns an HTTP 429 response with the text body "Number of allowed API requests per minute exceeded". Because throttling is scoped per application per account, an add-on connected to two different customers' ServiceM8 accounts is throttled separately for each account.

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

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

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

Tagged areas include Field Service, Job Management, Rate Limiting, Quotas, and Throttling.

3 Limits Throttle: 429
Field ServiceJob ManagementRate LimitingQuotasThrottling

Limits

Requests Per Minute application-account
requests · minute
180
180 requests per minute per application per connected account. HTTP 429 on exceed.
Requests Per Day application-account
requests · day
20000
20,000 requests per day per application per connected account. HTTP 429 on exceed.
SMS Sending account
messages
plan credit pack
Outbound SMS via the Messaging API consumes the account's SMS credits and incurs charges beyond the plan pack.

Policies

Per-Application Per-Account Scoping
Throttling counters are tracked separately for each application connected to each ServiceM8 account.
Backoff and Caching
On a 429, use a cached value from a prior call, notify the end user, or retry later with backoff.
Prefer Webhooks Over Polling
Subscribe to object/event webhooks to receive change notifications instead of polling collections, reducing request volume.

Sources