Skip to main content
  • The StopWatch API can only be used by our 💫 Unlimited subscribers. Review all subscription options here.
  • The StopWatch API is only relevant to customers using App Objects Mode. For customers using the legacy Custom Objects Mode, please use HubSpot’s Custom Objects API directly.
The StopWatch API acts as a secure proxy for specific HubSpot CRM Objects and Properties APIs, relevant to the StopWatch for HubSpot app. It is specifically designed to allow programmatic read-only access to StopWatch Time Log records, bypassing the scope restrictions imposed by HubSpot on App Objects.

Secure Auth

Industry-standard Bearer token authentication with hashed storage.

Smart Pagination

Automatic rewriting of HubSpot pagination links for intuitive paging.

Header Forwarding

Critical HubSpot metadata (like rate limits) is passed directly to your app.

Fully Versioned

Built for long-term stability with versioned endpoints.

​
Why use the StopWatch API?

HubSpot restricts the programmatic access to App Object records to the developer providing the given app. This means that while our customers can see their StopWatch Time Log records in HubSpot’s UI, they cannot extract them programmatically using standard HubSpot API authentication methods. The StopWatch API provides a secure layer that uses the StopWatch App’s permissions to fetch records on your behalf, giving you the access you need to programmatically read your StopWatch Time Log records.

​
Base URL

The API’s base URL is: 
https://api.threadi.au

​
Authentication

All requests to the StopWatch API must include an Authorization header with a static bearer . 
Authorization: Bearer {token}
API keys can be managed from within HubSpot, within the app’s Admin Settings tab. Only the account’s Primary Admin can manage API keys. See our Usage Guide’s App Settings section for more information.
By default, each API key is rate-limited to 1,000 requests per day (UTC). If you need a higher daily limit, please submit a support request.

​
Key Features

When you fetch a list of StopWatch Time Log records, HubSpot . We automatically rewrite these links so you can use them directly in your next request: 
"paging": {
  "next": {
    "after": "12345",
    "link": "https://api.threadi.au/stopwatch/v1/timelogs?limit=10&after=12345"
  }
}

​
Response Headers

The following x-stopwatch-* headers are supplied in the majority of cases:
keyexample
1000
123
1774913275000
We also forward all x-hubspot-* headers from the underlying HubSpot response. This allows your integration to monitor rate limits in real-time. These headers could include:
  • x-hubspot-correlation-id
  • x-hubspot-ratelimit-interval-milliseconds
  • x-hubspot-ratelimit-max
  • x-hubspot-ratelimit-remaining
  • x-hubspot-ratelimit-secondly
  • x-hubspot-ratelimit-secondly-remaining
Learn more about how to interpret these HubSpot headers here.
Next, explore our API Reference to start building.