One post per hour, per destination
Every destination has its own hourly slot: your profile is one, and each club is another. Slots are never pooled — posting to one does not use up another, and a free slot elsewhere does not help a busy one.
When a slot is taken you get 429 with a Retry-After header (in seconds) and the details in the body:
HTTP/1.1 429 Too Many Requests
Retry-After: 2400
{
"success": false,
"error": {
"code": "PUBLIC_API_RATE_LIMITED",
"message": "This club already had its post this hour",
"details": {
"destination": "club",
"clubId": "00000000-0000-0000-0000-000000000000",
"retryAfterSeconds": 2400,
"nextAllowedAt": "2026-10-05T19:00:00.000Z"
}
},
"requestId": "…"
}
Wait at least Retry-After seconds, or until nextAllowedAt, before posting to that destination again. Do not retry in a loop.