Kobiton · Rate Limits

Kobiton Rate Limits

Kobiton does not publish fixed numeric request-per-minute rate limits for its REST API. In practice the binding constraint on test throughput is not an API request cap but two account-level limits: the monthly testing-minutes allowance of your plan (500 / 3,000 / 7,500 minutes on the self-serve tiers) and how many real devices you can hold at once. Public-cloud device concurrency is governed by device availability and plan, and a device is exclusively booked for the duration of a manual or automated test run. The Appium hub inherits the same device-booking and minute constraints.

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

It captures 4 rate-limit definitions, measuring requests, minutes, devices, and idle-minutes.

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

Tagged areas include Mobile Testing, Test Runs, Device Cloud, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Mobile TestingTest RunsDevice CloudRate LimitingQuotas

Limits

REST API Request Rate account
requests
not published
No fixed numeric per-minute request-rate limit is documented for the REST API.
Monthly Testing Minutes account
minutes
per plan (500 / 3,000 / 7,500 self-serve)
Test runs (manual, scripted, and scriptless) draw down the plan's monthly minute allowance.
Device Concurrency account
devices
governed by plan and device availability
A real device is exclusively booked for the duration of a session; concurrent runs need concurrent devices.
Session Idle Timeout session
idle-minutes
~10 minutes (default, adjustable in manual session settings)
Manual sessions end after an idle period unless the idle-quit setting is disabled.

Policies

Device Booking
Devices are allocated exclusively per session; release the device promptly to free capacity and stop consuming minutes.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Minute Conservation
Scope scriptless and data-driven runs and end idle sessions to avoid burning the monthly minute allowance.

Sources