> ## Documentation Index
> Fetch the complete documentation index at: https://docs.casefile.win/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits and refusals

> Your plan's limits, and every reason the door refuses an event.

Your plan sets how many events your organization may send a second and a month.
The door refuses an event past either, and every refusal names its reason in the answer's error.

## Limits by plan

| Plan | Events a second | Events a month |
| - | - | - |
| Starter | 10 | 1,000,000 |
| Team | 400 | 100,000,000 |
| Scale | 4,000 | 1,000,000,000 |

A trial has the Team plan's limits.
Each accepted event's answer gives the limit a second as it stands now, in `limitPerSecond`.

## Refusals

| Status | Error | What it means |
| - | - | - |
| `400` | The first thing wrong | The event is not one the door can read. The error names the first thing wrong with it. |
| `401` | `unknown key` | The key is missing, is not a door key, or is not one Casefile knows. |
| `403` | `read only` | The organization has an invoice to pay. Events are refused until it is paid, so sending again changes nothing. |
| `403` | `monthly events used` | The plan's events for this month are used up. Events are refused until the month ends, so sending again changes nothing. |
| `429` | `over limit` | The organization is sending more events a second than its limit. Wait 1 second, as Retry-After says, then send the same event again. |
| `429` | `limit busy` | Another of the organization's events was waiting for room under its limit at the same moment. Wait 1 second, as Retry-After says, then send the same event again. |
| `429` | `intake is behind` | Casefile is behind on reading events, and the organization is sending more than its share. Wait 5 seconds, as Retry-After says, then send the same event again. |
| `429` | `too many keys to check` | The door was sent more keys it has not seen than it looks up for now, from this address or from everyone. It says this before it looks the key up, so it tells nothing about whether the key exists. Wait as long as Retry-After says, then send the same event again. |
| `503` | `keys unavailable` | The door cannot check keys just now. Wait 5 seconds, as Retry-After says, then send the same event again. |
| `503` | `limits unavailable` | The door cannot check the limit just now. Wait 1 second, as Retry-After says, then send the same event again. |
| `503` | `archive unavailable` | The door cannot store the event just now. Wait 1 second, as Retry-After says, then send the same event again. |
| `503` | `intake unavailable` | The door stored the event but cannot pass it on just now. Wait 1 second, as Retry-After says, then send the same event again. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.