Tray.ai · Rate Limits

Tray Ai Rate Limits

Machine-readable rate limit definitions for Tray.ai's Platform API and Embedded API. Values reflect the limits documented in Tray's developer portal. Verbatim from the Platform API docs: "all endpoints are rate limited at 30 requests per second or 1800 requests per minute." The Embedded API docs match: "All endpoints are rate limited to 30 requests per second." The Call Connector endpoint is additionally capped at 1,000 concurrent requests. Trigger API event delivery is not rate limited.

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

It captures 7 rate-limit definitions, measuring requests_per_second, requests_per_minute, concurrent_requests, and events.

The profile also includes 5 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.

Tagged areas include Automation, Integration, iPaaS, Rate Limiting, and Quotas.

7 Limits Throttle: 429 Quota: 429
AutomationIntegrationiPaaSRate LimitingQuotasThrottling

Limits

Platform API Steady-State account
requests_per_second · second
30
Platform API Burst account
requests_per_second · second
50
Platform API Per-Minute Equivalent account
requests_per_minute · minute
1800
Call Connector Concurrency account
concurrent_requests · instant
1000
Trigger Event Delivery account
events · instant
-1
Embedded API Steady-State account
requests_per_second · second
30
Embedded API Burst account
requests_per_second · second
50

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor the Retry-After header when present in a 429 response.
Burst Handling
Short bursts up to 50 RPS are tolerated before steady-state throttling engages on both the Platform and Embedded APIs.
Concurrency
The Call Connector endpoint enforces a 1,000-concurrent-request ceiling; long-running connector calls should be parallelized within that ceiling.
Event Delivery
Trigger event delivery is not rate limited and is best-effort real-time. Consumers must size webhook receivers accordingly.
Fair Use
Even though Trigger event delivery is uncapped, sustained patterns that materially impact shared infrastructure may be subject to fair-use review by Tray.