canonical: https://jentic.com/apis/timetoreply.com/timetoreply

# timetoreply API

timetoreply email analytics API for tracking reply times, SLA compliance, team performance, and generating reports. The API exposes 20 endpoints secured with bearer authentication.

## For AI agents

Programmatically get overview report with stats on threads, messages, and reply times, get productivity metrics report. Covers 20 operations with bearer authentication.

## Scope

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

## Capabilities

- Get overview report with stats on threads, messages, and reply times
- Manage analytics data programmatically
- Integrate timetoreply API into automated workflows
- Query and filter timetoreply API records by parameters
- Monitor timetoreply API operational status and events

## Use cases

### Analytics Operations

Use the timetoreply API to perform analytics operations programmatically. The API provides 20 endpoints covering core functionality including get overview report with stats on threads, messages, and reply times, get productivity metrics report, get comparative analysis report.

Example prompt: Call GET `/api/reports/overview` to get overview report with stats on threads, messages, and reply times

### Automated Auth Management

Automate auth operations by combining multiple timetoreply API endpoints. Agents can get productivity metrics report and then get comparative analysis report in a single workflow.

Example prompt: Call GET `/api/reports/productivity` to get productivity metrics report, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'get overview report with stats on threads, messages, and reply times', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/reports/overview` | Get overview report with stats on threads, messages, and reply times |
| GET | `/api/reports/productivity` | Get productivity metrics report |
| GET | `/api/reports/comparative` | Get comparative analysis report |
| GET | `/api/reports/interactions` | Get interactions report |
| GET | `/api/reports/sla` | Get SLA compliance report |
| GET | `/api/reports/trend` | Get trend analysis report |
| GET | `/api/reports/contact` | Get contact report |
| GET | `/api/reports/teams` | Get teams report |

## Key resources

- **Auth** — Operations related to Auth
- **Entities** — Operations related to Entities
- **Logs** — Operations related to Logs
- **Reports** — Operations related to Reports

## Why Jentic

- **Setup:** Wiring the timetoreply API by hand means handling its bearer token, assembling the query parameters each report expects, and managing retries yourself. Through Jentic you install once, import timetoreply from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** timetoreply serves read-only reports selected by query parameters rather than a resource id in the URL path, so scope the agent by the operations it needs, such as the overview or productivity report. You choose that set, so reports you do not name stay unavailable.
- **Credential handling:** Your timetoreply 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 'get a reply-time overview' or 'compare team SLA performance', and Jentic returns the matching timetoreply 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 timetoreply API use?

The timetoreply API uses a Bearer token in the Authorization header. 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 get overview report with stats on threads, messages, and reply times with the timetoreply API?

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

### What are the rate limits for the timetoreply 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 get overview report with stats on threads, messages, and reply times through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get overview report with stats on threads, messages, and reply times'. Jentic returns the matching timetoreply API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The timetoreply API exposes 20 endpoints covering auth, entities, logs operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which timetoreply operations the agent may call and which credentials it may use. The timetoreply API is read-only and serves reports chosen by query parameters, so you can grant only the reports the agent needs, such as GET `/api/reports/overview` or GET `/api/reports/productivity`, and leave the SLA, comparative, or teams reports out. Reports you do not name stay unavailable to the agent.