Deel · Rate Limits

Deel Rate Limits

Deel exposes per-token request limits documented in their developer docs. When a limit is exceeded, the API returns HTTP 429 and clients are expected to honor the Retry-After header with exponential backoff and jitter.

3 Limits Throttle: 429
HRPayrollGlobal HiringEORContractorsRate LimitingThrottling

Limits

Per Token Default token
requests
Default sliding-window limit applied per API token. Clients receive 429 Too Many Requests with Retry-After when exceeded.
Bulk / Listing Endpoints token
requests
List and search endpoints (e.g. GET /people, GET /contracts) carry tighter limits than item-level endpoints; paginate aggressively.
Webhook Delivery subscription
events
Outbound webhook deliveries are batched per subscription with retries on 5xx responses; clients must respond within the timeout window.

Policies

Backoff Strategy
Implement exponential backoff with jitter on 429 responses; honor the Retry-After header and avoid retrying with the same Idempotency-Key until the backoff window has elapsed.
Idempotency
Use Idempotency-Key header on POST/PATCH state-changing operations to safely retry without creating duplicate resources.
Pagination
Use cursor or page-based pagination on list endpoints to stay within list-endpoint limits.

Sources