Timelyapp Timely API Docs
53
AI ReadinessNon-Ready (C)53/100
Community OpenAPI document · agent-readyAnalyticsWeb Analyticsbearer, oauth275 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically webhook event types, bulk import time entries (create/update/delete). Covers 75 operations with bearer, oauth2 authentication.
Use for: I need to webhook event types, I want to bulk import time entries (create/update/delete), Search for bulk import events (create/update/delete), Find all client create
Not supported: Does not handle payments, communications, or crm - use for analytics only.
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.
Install Jentic One Beta
Connect the Timely API Docs to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Timely API Docs, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftimelyapp.com%2Ftimelyapp" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Ftimelyapp.com%2Ftimelyapp" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Timely API Docs API.
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
Patterns agents use Timely API Docs API for, with concrete tasks.
★ 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).
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.
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.
Search Jentic for 'webhook event types', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
75 endpoints — the timely api allows you to integrate time tracking into your applications and workflows.
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
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
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
T
Timely API Docs
- Non-Ready (C)53/100
34
Foundational Compliance59
Developer Experience & Jentic Compatibility41
AI-Readiness & Agent Experience90
Agent Usability75
Security75
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
34
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: FSignals: 4
36%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
5%
Example Density
How richly the API is illustrated with examples.
86%
Example Validity
Percentage of examples that conform to their schemas.
43%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
41
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
37%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
87%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
40%
Summary Coverage
Coverage of summaries across operations/tags/info.
90
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
90%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
75
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
75%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Timely API Docs API through Jentic.
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.
GET STARTED