Rate limits

What this is

Two limits apply, both answering 429 with a Retry-After header in seconds:

Limit	Scope
600 requests / 10 minutes	Per client address, not per key - several keys used from the same address share one bucket.
60 requests / hour	POST /posts, per workspace - every key and every signed-in person combined.

The per-workspace post-creation limit exists so one runaway script or agent can’t exhaust the whole team’s ability to schedule, regardless of which key it used. The address-based limit means two integrations behind the same outbound IP (two services on one server, for example) share the 600/10min budget - size accordingly.

Common errors

Error	Cause	Fix
429 on most routes	Over 600 requests in 10 minutes from this address.	Wait for the window named in Retry-After, then retry.
429 specifically on POST /posts	Over 60 post-creations in an hour across the whole workspace.	Wait for Retry-After; if this is routine, batch fewer, larger POST /posts calls (it accepts multiple targets per call) instead of one call per account.