Check Point · Rate Limits

Checkpoint Rate Limits

Check Point does not publish a single, unified rate-limit policy for its API portfolio. Each API is bound to the customer's product deployment (on-prem Management Server, Smart-1 Cloud, Infinity Portal tenant, CloudGuard, Harmony Email, Spark Management) and the practical request ceiling is governed by deployment sizing rather than a published per-second number. The Management API documents a session-based model (login, run commands, publish, logout) where concurrency is bounded by the number of API sessions configured on the management server.

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

It captures 2 rate-limit definitions, measuring concurrent_requests and varies.

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 and serviceUnavailable.

Tagged areas include Cloud Security, Cybersecurity, Network Security, Security, and Rate Limiting.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Cloud SecurityCybersecurityNetwork SecuritySecurityRate Limiting

Limits

Management API session concurrency management-server
concurrent_requests
see deployment sizing — typically bounded by configured api-sessions on the management server
The Check Point Management API uses session-based concurrency. Limits are determined by the management server configuration, not a published per-second cap.
CloudGuard / Harmony / Infinity Portal APIs tenant
varies
see Infinity Portal admin guide; not publicly documented
Cloud-hosted APIs may apply tenant-scoped throttling but Check Point does not publish the numeric ceilings.

Policies

Session Lifecycle (Management API)
Clients call /login to obtain a session token (sid), perform commands, then /publish and /logout. Long-lived sessions block other writers; close sessions promptly.
Backoff Strategy
On 429 / 503, apply exponential backoff with jitter and retry. Sustained pressure should be discussed with Check Point TAC.
Deployment Sizing
Practical throughput depends on management-server CPU/RAM and the configured api-sessions pool. Resize the management server rather than expecting cloud-style horizontal scale.

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