Hubstaff · Rate Limits

Hubstaff Rate Limits

Hubstaff publishes a single global rate limit for API v2 - authenticated users are allowed 1,000 requests every hour, per application. Individual requests are subject to a 30-second timeout. All requests must be made over HTTPS (plain HTTP is redirected). Personal access tokens act as OAuth refresh tokens and expire after 90 days, so token-exchange calls against account.hubstaff.com should be cached rather than performed per request. Collection endpoints are cursor-paginated with page_start_id and page_limit; Hubstaff recommends the pre-aggregated activities/daily endpoints over raw activities when building reports, because they return far fewer records for the same time span.

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

It captures 4 rate-limit definitions, measuring requests, seconds, days, and records.

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

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

4 Limits Throttle: 429
Time TrackingTimesheetsWorkforce ManagementRate LimitingQuotas

Limits

API Requests user + application
requests
1000 per hour
Authenticated users are allowed 1,000 requests every hour, per application.
Request Timeout request
seconds
30
Individual API requests time out after 30 seconds.
Personal Access Token Lifetime token
days
90
PATs are OAuth refresh tokens with a 90-day expiry; exchange them for short-lived access tokens and rotate before expiry.
Page Size request
records
configurable via page_limit
Collection endpoints use cursor pagination (page_start_id / page_limit).

Policies

HTTPS Only
All requests must use HTTPS; HTTP requests are redirected to HTTPS.
Prefer Daily Aggregates
Use the activities/daily endpoints instead of raw 10-minute activities where possible - they are pre-aggregated and consume far less of the hourly request budget for reporting workloads.
Backoff Strategy
Spread bulk reads across the hour and implement exponential backoff with jitter on 429 responses to stay within the 1,000 requests/hour per-app budget.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/hubstaff-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.