canonical: https://jentic.com/apis/timelyapp.com/timelyapp # Timelyapp Timely API Docs The Timely API allows you to integrate time tracking into your applications and workflows. Use it to sync projects, log time entries, export reports, and automate time management. Authentication This API uses OAuth 2.0 for authentication. OAuth 2.0 Authorization Code Flow 1. **Create an OAuth Application**: Go to `https://app.timelyapp.com/{account_id}/oauth_applications` (admin access required) 2. The API exposes 75 endpoints secured with bearer, oauth2 authentication. ## For AI agents Programmatically webhook event types, bulk import time entries (create/update/delete). Covers 75 operations with bearer, oauth2 authentication. ## Scope Does not handle payments, communications, or crm - use for analytics only. ## Capabilities - Webhook event types - Bulk import time entries (create/update/delete) - Client create - List all clients of an account - Monitor Timely API Docs operational status and events ## Use cases ### Analytics Operations Use the Timely API Docs to perform analytics operations programmatically. The API provides 75 endpoints covering core functionality including webhook event types, bulk import time entries (create/update/delete), bulk import events (create/update/delete). Example prompt: Call GET /webhook-events to webhook event types ### Automated Events Management Automate events operations by combining multiple Timely API Docs endpoints. Agents can bulk import time entries (create/update/delete) and then bulk import events (create/update/delete) in a single workflow. Example prompt: Call POST /1.1/{account_id}/bulk/hours to bulk import time entries (create/update/delete), then verify the result ### AI Agent Integration via Jentic AI agents discover and call Timely API Docs endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually. Example prompt: Search Jentic for 'webhook event types', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /webhook-events | Webhook event types | | POST | /1.1/{account_id}/bulk/hours | Bulk import time entries (create/update/delete) | | POST | /1.1/{account_id}/bulk/events | Bulk import events (create/update/delete) | | POST | /1.1/{account_id}/clients | Client create | | GET | /1.1/{account_id}/clients | List all clients of an account | | GET | /1.1/{account_id}/clients/{id} | Client details | | PUT | /1.1/{account_id}/clients/{id} | Client update | | POST | /1.1/{account_id}/day_properties | Create or update day properties | ## Key resources - **Events** — Track and manage time entries (events) - **Event Timers** — Start and stop timers on events - **Event States** — Workflow states for events - **Projects** — Project and budget management - **Clients** — Client management ## Why Jentic - **Setup:** Wiring the Timely API by hand means choosing between its bearer token and OAuth2 flows, threading the account id through every path, and handling retries yourself. Through Jentic you install once, import Timely from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** Timely puts the account id and record id in the URL path (/1.1/{account_id}/clients/{id}), so a rule can pin your agent to one account and its clients: it works within that account and nothing else. You choose the operations it may call, so writes like bulk hour posting are not included unless you add them. - **Credential handling:** Your Timely token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'list clients for an account' or 'post hours in bulk', and Jentic returns the matching Timely operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Mixpanel** — Alternative analytics API - **Amplitude** — Alternative analytics API - **Segment** — Complementary analytics API - **Pendo** — Complementary analytics API ## FAQ ### What authentication does the Timely API Docs use? The Timely API Docs uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I webhook event types with the Timely API Docs? Yes. Use the GET /webhook-events endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Timely API Docs? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I webhook event types through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'webhook event types'. Jentic returns the matching Timely API Docs operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Timely API Docs have? The Timely API Docs exposes 75 endpoints covering events, event timers, event states operations. ### Can I limit what my agent is allowed to do with the Timely API? Yes. Because you run Jentic One yourself, your own rules decide which Timely operations and credentials your agent can use. Since Timely carries the account id and record id in the URL path, such as /1.1/{account_id}/clients/{id}, a rule can pin the agent to a single account and its clients and nothing beyond that. You also choose which operations it may call, so write actions like bulk hour posting to /1.1/{account_id}/bulk/hours stay off limits unless you explicitly add them.