Tekmetric · Rate Limits

Tekmetric Rate Limits

Tekmetric does not publish numeric rate limits for its partner API, since the API reference itself is gated behind manual approval. The only public evidence of rate-limit behavior comes from beetlebugorg/tekmetric-mcp, an independent open-source client that self-throttles to 10 requests/second (burst of 10) and retries on HTTP 429 and 5xx responses with exponential backoff - a defensive posture chosen by that client's author, not a limit confirmed as Tekmetric's actual server-side threshold.

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

It captures 2 rate-limit definitions, measuring requests.

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

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

2 Limits Throttle: 429
AutomotiveAuto RepairShop ManagementRate LimitingQuotas

Limits

Client-Side Global Rate Limit (third-party client) client
requests
10 requests/second, burst of 10 (self-imposed by tekmetric-mcp, not a published Tekmetric limit)
Not an officially documented Tekmetric limit; reflects one client's defensive throttling.
Tekmetric API Requests account
requests
not published
No numeric per-account or per-endpoint request-rate limit is publicly documented by Tekmetric.

Policies

Retry with Backoff
Third-party client behavior treats HTTP 429 and 5xx responses as temporary and retries with exponential backoff; not confirmed as an official Tekmetric-documented policy.
OAuth Token Reuse
The OAuth token endpoint is reported as idempotent - repeated calls return the same token rather than issuing a new one - and tokens are reported not to expire unless explicitly revoked by Tekmetric, reducing the need for frequent re-authentication calls.

Sources