API rate limits

Happier rate-limits its busiest endpoints. The defaults suit a normal deployment; you would usually only raise one after watching a specific endpoint throttle under real load, or lower one on a server exposed to the public internet.

Each endpoint has two environment variables — a maximum and a window. Set both or neither; setting only the maximum leaves the window at its default, which is rarely what you want.

The window accepts the same duration strings the defaults use (1 minute, 30 seconds, 1 hour).

What it counts against matters more than the number. Account limits are per signed-in account, so one busy user cannot exhaust another's budget. IP address limits apply before Happier knows who is calling — they protect unauthenticated routes, and behind a reverse proxy they are only as accurate as the forwarded client address your proxy sets. 27 of the 33 limits are per-account.

Two clusters are worth knowing about before a rollout, because they throttle exactly when many people onboard at once: auth.pairing.* covers connecting a new device, and connectedServices.deviceAuth.* covers linking an agent account from a headless machine.

Related

• Environment variables — everything else the server reads.
• Server quickstart