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: Pulse
providerId: pulse
created: '2026-05-04'
generated: '2026-08-29'
modified: '2026-08-29'
method: searched
source: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ovw.htm
tags:
  - Ivanti
  - Network Security
  - Secure Access
  - SSL VPN
  - VPN
  - Zero Trust
  - Rate Limiting
description: >-
  Rate-limit posture for the Ivanti secure-access APIs. Ivanti publishes NO rate limits,
  quotas, throttling policy or rate-limit response headers for the Ivanti Connect Secure /
  Ivanti Policy Secure configuration REST API or the Ivanti Neurons for Zero Trust Access
  REST API. limit_count is an honest zero.
limit_count: 0
limits: []
headers: {}
responseCodes: {}
policies: []
findings:
  - >-
    The provider's REST API Solutions Guide publishes an explicit "Error Codes Supported"
    table (200, 201, 204, 400, 401, 403, 404, 422, 500). 429 Too Many Requests is not in it,
    and no Retry-After behaviour is described.
  - >-
    No X-RateLimit-*, RateLimit-* or Retry-After header is documented anywhere in the ICS/IPS
    guide or the nZTA API guide.
  - >-
    This is architecturally consistent rather than an omission: ICS and IPS are appliances
    the customer operates, so throughput is bounded by the appliance the caller owns, not by
    a vendor quota. nZTA is a hosted tenant and could carry limits, but none are published.
  - >-
    Practical consequence for an agent: there is no runtime backpressure signal on these
    APIs. A client must self-pace, and cannot distinguish appliance overload from throttling
    — 500 "the ICS/IPS rest server is not responding" is the only congestion signal
    documented.
evidence:
  - url: https://help.ivanti.com/ps/help/en_US/ICS/22.x/apig/rest_api_soln_guide/ovw.htm
    status: 200
    checked: '2026-08-29'
    finding: >-
      Full error-code table published; no rate limit, quota, throttle or 429 anywhere on the
      page.
  - url: https://docs.ivanti.com/ps/help/en_us/nsa/22x/nsa-zta/api/api-calls
    status: 200
    checked: '2026-08-29'
    finding: >-
      Complete nZTA entity/operation reference; no rate limit or throttling statement.
provenance_note: >-
  Supersedes a 2026-05-04 bulk-sweep scaffold that asserted invented free/professional/
  enterprise tiers with 10/100/1000 requests-per-minute limits and X-RateLimit-* headers.
  None of that was published by Ivanti. Replaced 2026-08-29 with the searched result.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com