Skip to main content
TeamCare APIs use standard HTTP status codes to indicate the outcome of each request. Understanding these codes helps you diagnose issues quickly and respond appropriately in your integration. Every error response includes a relevant status code. For rate limit errors, the response also includes a Retry-After header so you know when it is safe to retry.

​
Error codes

​
Handling retries

For transient errors such as 429 and 500, implement retry logic with exponential backoff, respecting the Retry-After header on 429 responses.
All 429 responses include a Retry-After header with a value from 1 to 60. You must wait that many seconds before the next request, because rejected requests still count against the current rate limit window.
TeamCare APIs use standard HTTP status codes to indicate the outcome of each request. Understanding these codes helps you diagnose issues quickly and respond appropriately in your integration. Every error response includes a relevant status code. For rate limit errors, the response also includes a Retry-After header so you know when it is safe to retry.

​
Error codes

​
Handling retries

For transient errors such as 429 and 500, implement retry logic with exponential backoff, respecting the Retry-After header on 429 responses.
All 429 responses include a Retry-After header with a value from 1 to 60. You must wait that many seconds before the next request, because rejected requests still count against the current rate limit window.