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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-11.
Written by API Evangelist on 2026-07-11 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/kobiton-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.