OptiSigns · Rate Limits

Optisigns Rate Limits

OptiSigns serves a single GraphQL endpoint at https://graphql-gateway.optisigns.com/graphql, authenticated per API key. OptiSigns does not publish specific numeric rate limits (requests per minute/second or query complexity budgets) in its public developer docs. The developer materials note error handling and pagination as first-class concerns, which implies server-side throttling and paged result sets, but exact limits are not documented. Treat limits as unconfirmed and design clients defensively.

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

It captures 3 rate-limit definitions, measuring requests, query_cost, and items.

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.

3 Limits Throttle: 429
Digital SignageScreensGraphQLRate LimitingQuotasThrottling

Limits

GraphQL Requests api_key
requests
see provider documentation
OptiSigns does not publish a numeric request rate limit; assume server-side throttling per API key.
Query Complexity api_key
query_cost
see provider documentation
No published GraphQL query-complexity or depth budget; large queries should use pagination.
Result Pagination request
items
paginated
The docs describe pagination as a first-class concern; list queries return paged connections rather than unbounded sets.

Policies

Pagination
Use cursor/page arguments on list queries; do not request unbounded result sets.
Error Handling
Handle GraphQL errors and HTTP 429 responses; implement exponential backoff with jitter on throttling.
Plan Entitlement
API access itself is gated by plan (Pro Plus and higher); a 401/403 typically indicates a missing entitlement or invalid key rather than a rate limit.

Sources