Official vendor OpenAPI document · agent-readyAnalyticsBusiness IntelligenceapiKey, bearer159 EndpointsREST
For Agents
Programmatically create a new API key, list API keys. Covers 159 operations with apiKey, bearer authentication.
Use for: I need to a new API key, I want to API keys, Search for API key details, Find all an API key
Not supported: Does not handle payments, communications, or crm - use for analytics only.
Timesheet is a cross-platform time tracking application for professionals, freelancers, and teams to monitor work hours, manage projects, track expenses, and generate detailed reports across Android, iOS, and Web. The Timesheet REST API provides comprehensive functionality for creating, retrieving, updating, and deleting time tracking data. Integrate time tracking, project management, and reportin. The API exposes 159 endpoints secured with apiKey, bearer authentication.
Install Jentic One Beta
Connect the Timesheet API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Timesheet API, 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%2Ftimesheet.io%2Ftimesheet" | 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%2Ftimesheet.io%2Ftimesheet" | 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 Timesheet API.
Create a new API key
List API keys
Get API key details
Delete an API key
Revoke all API keys
Use Cases
Patterns agents use Timesheet API for, with concrete tasks.
★ Analytics Operations
Use the Timesheet API to perform analytics operations programmatically. The API provides 159 endpoints covering core functionality including create a new API key, list API keys, get API key details.
Call POST /v1/apikeys to create a new API key
Automated Oauth2 Authentication Management
Automate oauth2 authentication operations by combining multiple Timesheet API endpoints. Agents can list API keys and then get API key details in a single workflow.
Call GET /v1/apikeys to list API keys, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Timesheet API 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 apiKey, bearer tokens manually.
Search Jentic for 'create a new API key', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
159 endpoints — timesheet is a cross-platform time tracking application for professionals, freelancers, and teams to monitor work hours, manage projects, track expenses, and generate detailed reports across android, ios, and web.
METHOD
PATH
DESCRIPTION
POST
/v1/apikeys
Create a new API key
GET
/v1/apikeys
List API keys
GET
/v1/apikeys/{keyId}
Get API key details
DELETE
/v1/apikeys/{keyId}
Delete an API key
POST
/v1/apikeys/revoke-all
Revoke all API keys
POST
/v1/apikeys/{keyId}/revoke
Revoke an API key
POST
/v1/automations
Create automation
GET
/v1/automations
List automations
POST
/v1/apikeys
Create a new API key
GET
/v1/apikeys
List API keys
GET
/v1/apikeys/{keyId}
Get API key details
DELETE
/v1/apikeys/{keyId}
Delete an API key
POST
/v1/apikeys/revoke-all
Revoke all API keys
POST
/v1/apikeys/{keyId}/revoke
Revoke an API key
POST
/v1/automations
Create automation
GET
/v1/automations
List automations
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
Timesheet API
- Foundational (C)57/100
81
Foundational Compliance65
Developer Experience & Jentic Compatibility36
AI-Readiness & Agent Experience63
Agent Usability63
Security85
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
81
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
94%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
65
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
5%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
55%
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.
36
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
34%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
50%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
63
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: B-Signals: 1
63%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
63
Security
Trust, risk posture, and security compliance.
Grade: B-Signals: 1
62%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
85
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: ASignals: 1
85%
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 Timesheet API by hand means choosing between its Authorization API key and bearer token, working through 159 endpoints, and handling retries yourself. Through Jentic you install once, import Timesheet from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Timesheet puts the key id in the URL path (/v1/apikeys/{keyId}), so a rule can pin your agent to a specific API key resource. You choose the operations it may call, so destructive ones like revoking a key or revoke-all are not included unless you add them.
Credential isolation
Your Timesheet credential 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 API keys' or 'create an automation', and Jentic returns the matching Timesheet 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 Timesheet API through Jentic.
What authentication does the Timesheet API use?
The Timesheet API uses apiKey, bearer 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 create a new API key with the Timesheet API?
Yes. Use the POST /v1/apikeys endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Timesheet API?
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 create a new API key through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new API key'. Jentic returns the matching Timesheet API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Timesheet API have?
The Timesheet API exposes 159 endpoints covering oauth2 authentication, API key authentication, pagination operations.
Can I limit what my agent is allowed to do with the Timesheet API?
Yes. Because you run Jentic One yourself, your own rules decide which Timesheet API operations and credentials the agent may call, so you can grant read operations like GET /v1/apikeys or GET /v1/automations while withholding everything else. The key id sits in the URL path (/v1/apikeys/{keyId}), so a rule can pin the agent to a specific API key resource rather than the whole account. Destructive operations such as revoking a key or POST /v1/apikeys/revoke-all are only available to the agent if you explicitly add them.
GET STARTED