429 on /api/v2/users bulk updates - backoff strategy?

Is there a standard exponential backoff implementation recommended by the team for bulk user updates? I’m hitting 429 Too Many Requests on POST /api/v2/users when pushing updates via the Python SDK. The docs say: “Rate limits are applied per organization and are reset every minute.” My current script just retries immediately, which obviously fails. I’ve tried adding a 1-second delay, but it still trips the limit when processing 500+ users. Here’s the snippet:

response = client.users_api.post_users(users=users)
if response.status_code == 429:
 time.sleep(1)
 response = client.users_api.post_users(users=users)

Is there a specific header like Retry-After I should be parsing? The response doesn’t seem to include it. Just getting a generic 429 with no useful payload. Any code examples for handling this properly?

The 1s delay is too aggressive. Check the Retry-After header in the 429 response, it usually tells you exactly how long to wait. Don’t guess.