Skip to main content

rate-limit-exceeded

Type URI: https://developer.risepeople.com/errors/rate-limit-exceeded HTTP status: 429 Too Many Requests Format: application/problem+json (RFC 7807)

When this fires​

Your traffic exceeded one of two per-minute caps documented on the Rate limits page:

  • Per client_id — your authenticated app sent more requests in the current 60-second window than the per-app cap allows.
  • Per IP — total traffic from your source IP across all apps and unauthenticated endpoints exceeded the per-IP cap.

The response always includes a Retry-After header telling you how many seconds to wait.

Example response​

HTTP/1.1 429 Too Many Requests
Content-Type: application/problem+json
Retry-After: 42

{
  "type":   "https://developer.risepeople.com/errors/rate-limit-exceeded",
  "title":  "Too Many Requests",
  "status": 429,
  "detail": "Rate limit exceeded. Try again in 42 seconds.",
  "instance": "/v1/employees"
}

How to fix it​

  1. Respect Retry-After exactly. Don't retry sooner.
  2. Read X-RateLimit-Remaining on every successful response and back off before you hit zero — pacing is cheaper than 429s.
  3. Serialize parallel batch jobs. Many 429s come from short bursts of parallel calls; running them serially at 10 req/s is well under any cap.
  4. Cache responses that don't change. Avoid re-fetching the same employee record dozens of times in one workflow.
  5. Need a higher cap for a certified integration? Email developers@risepeople.com with your client_id, expected sustained RPS, and a brief description of the use case.

See Rate limits → Recommended backoff for a reference implementation in Node.