ScreenCloud · Rate Limits

Screencloud Rate Limits

ScreenCloud does not publish fixed numeric rate limits for the Studio GraphQL API. Practical usage limits are governed by your subscription (the number of licensed screens on your plan) rather than by a documented per-minute request cap. As with any GraphQL API, request cost varies with query depth and the number of nodes requested, and bulk mutations (for example bulkUpdateScreenContent or sendCommandToScreensByScreenIds) act on many screens per call.

Screencloud Rate Limits is the machine-readable rate-limit profile for ScreenCloud on the APIs.io network, in the API Commons Rate Limits shape.

It captures 4 rate-limit definitions, measuring requests, nodes, and screens.

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 Digital Signage, Screens, GraphQL, Rate Limiting, and Quotas.

4 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-05.
Written by API Evangelist on 2026-07-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Digital SignageScreensGraphQLRate LimitingQuotas

Limits

Studio GraphQL API Requests token
requests
not published
No fixed numeric request-rate limit is documented for the Studio GraphQL endpoint.
Query Complexity request
nodes
not published
GraphQL request cost scales with query depth and node count; deep or wide queries may be rejected or slowed. Modeled, not published.
Licensed Screens account
screens
per plan
The number of screens you can manage is bounded by paid screen licenses on your Core, Pro, or Enterprise subscription.
Bulk Mutation Fan-Out request
screens
configurable per call
Bulk operations act on the list of screen IDs supplied; batch sizes are governed by the caller and by any internal limits, which are not published.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Pagination
List queries expose ordering and pagination (OrderBy enums, cursor connections); page results rather than requesting unbounded lists.
Least-Privilege Tokens
Create API tokens with only the permissions needed rather than granting full access, to bound the blast radius of any single token.

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/screencloud-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.