API Usage and Rate Limits
Updated 2026-03-17
API Usage and Rate Limits
The Timehive API is hosted on a high-availability edge network to ensure reliability during high traffic loads. All external ingestion and statistics requests should be directed to https://api.timehive.io.
Endpoints
The Timehive API provides two main endpoints:
| Endpoint | Method | Description |
|---|---|---|
https://api.timehive.io/ingest |
POST | Ingestion API for logging events to your ledger. |
https://api.timehive.io/stats |
GET | Client Stats API for programmatically fetching your organization's total metrics. |
For detailed information on the request payloads and response structures, please refer to the API Reference documentation.
Rate Limits
API usage is strictly governed by the limits defined in your current Timehive subscription plan. These limits ensure fair usage and maintain performance across the platform.
- If you exceed your daily limit, the API will return a
429 Too Many RequestsHTTP status code. - You can view your current usage and limits within the User Dashboard.
- To handle high-throughput bursts, the Ingestion API utilizes a temporal event grouping system (merging consecutive events for the same task over a brief window).
Deprecation Notice: The legacy endpoints (
/api/ingest and /api/stats) on the main application domain have been deprecated. Please update your client integrations to use the new edge API domain (api.timehive.io).