Sirion · Rate Limits

Sirion Rate Limits

Sirion does not publish public numeric rate limits for its Business API & Integrations surface. Limits, quotas, and throughput are governed by the per-tenant enterprise agreement and configuration rather than a documented per-minute request cap. Sirion documents event-based and asynchronous processing for high-volume replication (for example, streaming Contract Requests to SAP Ariba), which implies queue-based backpressure rather than a hard public throttle. Any specific numbers here are unknown / MODELED.

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

It captures 3 rate-limit definitions, measuring requests, events, and records.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Contract Management, CLM, Enterprise, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-12.
Written by API Evangelist on 2026-07-12 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Contract ManagementCLMEnterpriseRate LimitingQuotas

Limits

Business API Requests tenant
requests
not published
No public numeric request-rate limit; governed by enterprise agreement.
Webhook Delivery tenant
events
not published
Event-based, asynchronous delivery with field-based filtering; volume tuned per tenant.
Async Replication Throughput tenant
records
not published
Documented event-based/async processing for CDR replication implies queue-based backpressure.

Policies

Asynchronous Processing
High-volume replication (e.g. Contract Requests to SAP Ariba) is event-based and asynchronous rather than synchronous request/response.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

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