AutoLeap · Rate Limits

Autoleap Rate Limits

The AutoLeap Partner API publishes default numeric rate limits per HTTP method, applied per partner account rather than per endpoint: 150 requests per minute for GET, and 50 requests per minute each for POST, PUT, and DELETE. AutoLeap documents these as defaults that "can be customized upon request." Exceeding the limit returns HTTP 429 (Too Many Requests).

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

It captures 4 rate-limit definitions, measuring requests.

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

Tagged areas include Auto Repair, Shop Management, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Auto RepairShop ManagementRate LimitingQuotas

Limits

GET Requests partner account
requests
150 per minute
Default; applies across all GET endpoints for the partner account, not per endpoint.
POST Requests partner account
requests
50 per minute
Default; covers bulk-create operations across Repair Orders, Customers, Vehicles, Items, Appointments, etc.
PUT Requests partner account
requests
50 per minute
Default; covers bulk-update operations.
DELETE Requests partner account
requests
50 per minute
Default; documented alongside POST/PUT even though most archival is done via PATCH in the current API surface.

Policies

Customizable Defaults
AutoLeap states default per-method limits can be raised on request for a given partner account.
Backoff Strategy
AutoLeap documentation recommends implementing retry logic with exponential backoff to handle 429 responses gracefully.
Token Lifetime
Access tokens expire after 1 hour and refresh tokens after 3 hours; AutoLeap recommends refreshing roughly every 55 minutes rather than re-authenticating, which also reduces load against the login endpoint.

Sources