specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Sepasoft
providerId: sepasoft
generated: '2026-08-27'
method: searched
source: https://docs.sepasoft.com/articles/user-manual/web-services
docs:
  - https://docs.sepasoft.com/articles/user-manual/web-services
  - https://docs.sepasoft.com/articles/user-manual/system-ws
created: '2026-05-04'
modified: '2026-08-27'
tags:
  - Rate Limiting
  - Throttling
description: >-
  Sepasoft publishes NO request-rate limits and NO rate-limit response headers, because it
  operates no hosted API - the Web Services module runs REST/SOAP endpoints on the
  customer's own Ignition Gateway, where throughput is bounded by that gateway. The only
  published ceilings are a licence-edition connection cap and operator-settable connection
  pool controls, both recorded below. The 2026-05-04 scaffold that previously occupied this
  file (invented free-tier 10 req/min and X-RateLimit-* headers) has been removed - none of
  those values were ever published by Sepasoft.
headers:
  documented: false
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  policy: null
  note: No RateLimit-* / X-RateLimit-* / Retry-After signalling is documented.
responseCodes:
  throttled: null
  note: No 429 semantics are documented for the RESTful endpoint framework.
limit_count: 1
limits:
  - name: Ignition Maker Edition simultaneous connection cap
    scope: licence-edition
    metric: simultaneous_connections
    limit: 1
    per: category
    categories:
      - REST Consumer
      - REST Provider
      - SOAP Consumer
      - SOAP Provider
    applies_to: Web Services Module 3.80.0 SP1 or newer installed on Ignition Maker Edition
    note: >-
      Verbatim from the Sepasoft docs - the same module installed on non-Maker Ignition
      behaves normally, i.e. this cap does not apply to commercial editions.
    source: https://docs.sepasoft.com/articles/user-manual/web-services
operator_controls:
  description: >-
    Consumer-side connection pooling is tunable by the operator through the system.ws
    scripting namespace. These are not limits Sepasoft enforces; they are knobs the
    customer sets on their own gateway.
  functions:
    - system.ws.setMaxTotalConnection
    - system.ws.setMaxConnectionPerRoute
    - system.ws.setDefaultMaxConnectionPerRoute
    - system.ws.setIdleConnectionTimeout
  source: https://docs.sepasoft.com/articles/user-manual/system-ws
gaps:
  - No published per-key, per-account or per-endpoint rate limit.
  - No rate-limit response headers and no documented 429 behaviour.