canonical: https://jentic.com/apis/tyme-app.com/tyme-app

# Tyme App Tyme API

Tyme time tracking app API for OAuth authentication, data synchronization, entity management, and webhooks. The API exposes 12 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically oauth login form, exchange auth code for tokens. Covers 12 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- OAuth login form
- Exchange auth code for tokens
- Refresh access token
- Bidirectional data sync
- Search entities
- Create or update entity
- Delete entities

## Use cases

### Developer Tools Operations

Use the Tyme API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including oauth login form, exchange auth code for tokens, refresh access token.

Example prompt: Call GET `/v1/authorize` to oauth login form

### Automated Authentication Management

Automate authentication operations by combining multiple Tyme API endpoints. Agents can exchange auth code for tokens and then refresh access token in a single workflow.

Example prompt: Call POST `/v1/access_token` to exchange auth code for tokens, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tyme 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 oauth2 tokens manually.

Example prompt: Search Jentic for 'oauth login form', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/authorize` | OAuth login form |
| POST | `/v1/access_token` | Exchange auth code for tokens |
| POST | `/v1/refresh_token` | Refresh access token |
| POST | `/v1/sync` | Bidirectional data sync |
| GET | `/data/search_entity` | Search entities |
| POST | `/data/update_entity` | Create or update entity |
| DELETE | `/data/entity` | Delete entities |
| GET | `/data/summary` | Get task summary |

## Key resources

- **Authentication** — Operations related to Authentication
- **Data** — Operations related to Data
- **Webhooks** — Operations related to Webhooks

## AI readiness

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.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 87 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/tyme-app.com/tyme-app/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Tyme API by hand means running its OAuth 2.0 authorize and token exchange, refreshing tokens before they expire, and matching each sync and entity operation to its request shape yourself. Through Jentic you install once, import the Tyme API from the API Directory, store the OAuth credential once, and your agent calls it.
- **Permission scoping:** The Tyme API carries its entity targets through the request body and query, so scope your agent to the operations it needs, such as searching entities or reading the summary. You choose the operations it may call, so a write like updating or deleting an entity is not included unless you add it.
- **Credential handling:** Your Tyme OAuth 2.0 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.
- **Discovery method:** Agents search Jentic by intent such as 'search for an entity' or 'get the data summary', and Jentic returns the matching Tyme API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Tyme API use?

The Tyme API uses OAuth 2.0 for authorization. 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 oauth login form with the Tyme API?

Yes. Use the GET `/v1/authorize` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tyme 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 oauth login form through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'oauth login form'. Jentic returns the matching Tyme API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Tyme API have?

The Tyme API exposes 12 endpoints covering authentication, data, webhooks operations.

### Can I limit what my agent is allowed to do with the Tyme API?

Yes. Because Jentic One is self-hosted, you decide which Tyme API operations your agent may call, so you can allow read-only actions like searching entities with GET `/data/search_entity` or reading the task summary with GET `/data/summary` while leaving everything else off. Write operations such as creating or updating an entity with POST `/data/update_entity` or deleting one with DELETE `/data/entity` are not available to the agent unless you explicitly add them. Your OAuth credential is injected at execution time under these rules, so the agent only ever reaches the operations you have permitted.