Rate limits
Most Jaah API endpoints have no rate limit. The few below do, because each one sends an email, charges a card, calls the payment provider, runs the Help assistant, accepts a trigger's webhook delivery or an issue tracker's event, runs an event automation now, sends a SIEM test event, sends a webhook delivery by hand or answers anyone without an account. Each limit is a sliding window: a call is refused while the calls counted in the last window already reach the limit, and it is allowed again as older calls age out. Most limits are counted by each Jaah server on its own, so calls spread across servers can go past them for as long as they stay spread. Three are counted across all servers: Add user email's 10 addresses a day, the 5 confirmation emails per user and address, and an event automation's hourly limit. Build on the numbers below, not on the gap.
When you are limited
A refused call gets 429 Too Many Requests and a sentence in detail (Webhooks answer {"code", "message"} in detail instead), for example:
{"detail": "Billing was changed too often. Try again in a few minutes."}
None of the limits below sends a Retry-After header, and only Send SIEM test event, Test webhook and Redeliver webhook delivery name their wait in detail. For the others that count
calls over a window, the wait depends on that window, from a minute to 24 hours: a call keeps being refused
until older calls leave it, so back off for up to the window named in the table. A refused call is not
counted against the limit that refused it — but where an endpoint has two limits, a call the second one
refuses has already been counted by the first. Add user email is the exception: its daily limit counts
only addresses added, so an add a confirmation-email limit refuses is not counted.
The limits
"Per organization" counts every call from your organization together, whoever makes it; "per user" counts your own calls. Where an endpoint has both, a call must fit both.
Open endpoints
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| List public plans | 600 per minute | caller's IP address | too many requests |
That budget is shared with most of Jaah's other calls that need no account, and with sign-out and switching organization, so those calls from the same address count against it too. A few, such as unsubscribing and confirming an email address, have budgets of their own.
People
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| Resend invitation | 3 per hour | invited user | Too many invitations for this user; try again later. |
| Resend invitation and Create user | 50 invitation emails per 24 hours | organization | Too many invitation emails from this organization today; try again tomorrow. |
Invitations sent by your identity provider's user provisioning count against the daily limit too.
Create user is never refused for this limit: the user is still created, and the response's
invitation is rate_limited instead of sent.
The per-user limit does not apply when the invited user already had a Jaah account and is joining your
organization from it. Resending to them counts only against the organization's daily limit, and a refused
resend says The invitation limit is reached; try again later.
Alerts
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| Add user email | 10 addresses per 24 hours | user, in each of their organizations | You can add 10 addresses a day. Try again tomorrow. |
| Add user email and Resend user email | 5 confirmation emails, then none until an hour after the last | user (across all their organizations) and address | Too many emails to this address. Try again in an hour. |
| Add user email and Resend user email | 5 confirmation emails per hour, and 10 per 24 hours | email address, whoever adds it | Too many emails to this address. Try again in an hour. |
| Add user email and Resend user email | 20 confirmation emails per hour | user, across all their organizations | Too many emails to this address. Try again in an hour. |
An address that is already confirmed is added without an email, so only the first limit counts it. The
second limit is not a sliding window: after its fifth email, an address waits a full hour from the last one.
When an address has had its 10 confirmation emails in 24 hours, detail still says to try again in an hour; the wait can be longer.
Verify user email has no rate limit, but after 5 wrong tries at one
emailed code it answers 422 with Too many wrong codes. Send a new one.
Billing
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| Create setup intent | 10 per hour, and 5 per 10 minutes per user | organization, user | Too many attempts to add a payment method. Try again later. |
| Change the plan | 10 per hour, and 5 per 10 minutes per user | organization, user | Too many attempts to subscribe. Try again later. |
| Cancel subscription, Undo subscription change, Preview an interval switch, Switch billing interval, Abandon checkout, Pay invoice, Quote a plan change and Change the plan | 30 per 10 minutes, all together | organization | Billing was changed too often. Try again in a few minutes. |
| List invoice lines | 120 per 10 minutes | organization | Billing was read too often. Try again in a few minutes. |
| Sync billing | 20 per 10 minutes | organization | Billing was refreshed too often. Try again in a few minutes. |
| Update billing details | 60 per 10 minutes | organization | Billing details were changed too often. Try again in a few minutes. |
| Refund a Jaah AI top-up | 5 per hour | organization | Too many refunds. Try again later. |
Change the plan spends both budgets: the 30-per-10-minutes one first, so a change the subscribe limit refuses has already been counted by it. Sending a change's request_id again to carry on a change already made counts against neither. Quote a product and Buy a product count against neither: they refuse a plan, which changes only through the two plan endpoints.
One more read has a budget, but is never refused. Get billing
shares the 60-per-10-minutes budget of Update billing details, and over it answers without details;
it also previews each next charge — the plan's and, when there is one, that of the hosting subscription — at most 60 times
per 10 minutes per organization for each of the two, and over that its next_charge.available (or
next_hosting_charge.available) is false.
Help assistant
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| Create conversation | 10 per 10 minutes | user | Too many new chats. Wait a few minutes or create a ticket. |
| Send message | 20 per 10 minutes | user | You're sending messages too fast. Wait a few minutes or create a ticket. |
Triggers
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| A delivery to a trigger's webhook URL | 120 per minute | webhook URL | Too many requests. |
| A delivery to a trigger's webhook URL | 600 per minute | sending IP address | Too many requests. |
| Run automation, on an event automation | Its Rate limit per hour (10 unless changed, at most 1000) | automation | Rate capped: N/hour reached, where N is its limit |
A webhook URL is not a Jaah API endpoint: it is the address a trigger shows for an outside system to post to. See Create an automation.
Run automation shares that hourly limit with the automation's deliveries: it counts every delivery in
the last hour that filed a task, is waiting to, or ran an action with no target (such as sending an
email), and its detail names the automation's own limit.
Issue trackers
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| An event a tracker sends to Jaah | 900 per minute | sending IP address and the connection the event names | Too many requests. |
| An event a tracker sends to Jaah | 300 per minute | tracker connection | Too many requests. |
Like a trigger's webhook URL, the address a tracker connection sends its events to is not a Jaah API endpoint. The first limit counts every event, before Jaah checks its signature; the second counts only events that pass that check, so a sender with the wrong secret never uses up the connection's own budget.
Audit
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| Send SIEM test event | 1 per 10 seconds | organization | A test event was just sent. Wait N seconds and try again. |
The detail names the seconds left to wait.
Webhooks
| Endpoint | Limit | Counted per | detail when refused |
|---|---|---|---|
| Test webhook and Redeliver webhook delivery | 1 per 10 seconds, both together | webhook endpoint | {"code": "too_soon", "message": "A delivery was just sent to this endpoint. Wait N seconds and try again."} |
The message names the seconds left to wait. Deliveries Jaah sends on its own are not counted.