Everhour · Rate Limits

Everhour Rate Limits

Everhour documents a single API-wide rate limit of around 20 requests per 10 seconds per API key, and explicitly notes the number is not guaranteed - it may vary with server load and may change. Exceeding the limit returns an HTTP 429 response with a Retry-After header specifying the number of seconds to wait before the next request. The limit is per API key (each user has their own key) and does not vary by pricing tier. List endpoints support pagination (time record endpoints up to 50,000 results per page, task lists up to 250 per page) to keep request counts down.

Everhour Rate Limits is the machine-readable rate-limit profile for Everhour on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests and results.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Time Tracking, Timesheets, Productivity, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Time TrackingTimesheetsProductivityRate LimitingQuotas

Limits

API Requests api key
requests
~20 requests per 10 seconds
Documented as approximate and not guaranteed; may vary with server load.
Time Records Page Size request
results
50000 per page
Max value of the limit parameter on team/user/task/project time endpoints.
Tasks Page Size request
results
250 per page
Max tasks per page on GET /projects/{id}/tasks.

Policies

Retry-After
429 responses include a Retry-After header with the number of seconds to wait before making another request.
Batch Requests
Contact Everhour before running large batches of API requests; they may offer a more convenient bulk retrieval path.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources