StackOne · Rate Limits

Stackone Rate Limits

StackOne is a unified-API gateway that fans every call out to a downstream SaaS provider (Workday, BambooHR, Greenhouse, etc.). Effective throughput is bounded by the downstream connector's own rate limits, which StackOne mirrors and surfaces to callers. StackOne's developer documentation does not publish a single platform-wide RPS figure; the contract is "respect the downstream connector limit" plus per-tier action-call quotas managed via billing.

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

It captures 3 rate-limit definitions, measuring varies and actions_per_month.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Integrations, iPaaS, Unified API, and Rate Limiting.

3 Limits Throttle: 429
IntegrationsiPaaSUnified APIRate Limiting

Limits

Per-Connector Downstream Limit linked-account/connector
varies
see downstream provider rate limits
StackOne forwards calls to the underlying SaaS connector (Workday, Greenhouse, BambooHR, etc.). The downstream provider's rate limit is the binding ceiling and is propagated back as the response.
Starter Plan Action-Call Quota account
actions_per_month · month
1000
Starter tier includes 1,000 action calls per month at no charge; additional calls are billed at $0.003 each rather than throttled.
Core / Enterprise Action-Call Volume account
actions_per_month
per contract
Volume on paid tiers is billed at $0.30 per 1,000 action calls (lower with volume discounts) rather than capped; soft limits are negotiated per contract.

Policies

Downstream Pass-Through
When a downstream SaaS returns 429, StackOne propagates the throttling response to the caller. Clients should honor Retry-After from the upstream connector and implement exponential backoff with jitter.
Action-Call Metering
Throughput control on paid tiers is primarily a billing meter (action calls), not a hard rate cap. Soft caps and burst behavior are documented per connector and per contract.
Connector-Specific Quirks
Specific connectors (e.g. Workday SOAP, NetSuite) have stricter session and concurrent-request limits; consult the per-connector documentation under docs.stackone.com for the binding numbers.

Sources