Splunk SOAR · Rate Limits
Splunk Soar Rate Limits
Splunk Soar Rate Limits is the rate-limit profile for Splunk SOAR on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Tagged areas include Security, SOAR, Automation, Orchestration, and Incident Response.
0 Limits
Transcribed from the provider's documentation on 2026-08-19 — help.splunk.com/en/splunk-soar/soar-cloud/rest-api-reference.
View Source
Limits
Splunk SOAR publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Splunk publishes no rate limits, quotas, throttling thresholds or rate-limit response headers for the Splunk SOAR REST API. The REST API reference, the "Using the Splunk SOAR REST API" section and the Splunk SOAR (Cloud) service description were all read on 2026-08-19 and none of them states a request ceiling, a window, a burst allowance, an X-RateLimit-*/RateLimit-* header, a Retry-After header or a 429 behaviour. This is consistent with the deployment model — SOAR runs on a single-tenant host (customer-hosted on-premises, or a dedicated SOAR Cloud tenant), so throughput is bounded by the tenant's own capacity rather than by a shared multi-tenant quota. The docs instead give performance ADVICE, captured below, which is not the same thing as a published limit. An agent cannot read a runtime backpressure signal from this API.
SecuritySOARAutomationOrchestrationIncident ResponseSOCSecurity OperationsPlaybooksCase ManagementThreat Intelligence
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.