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

# RescueTime APIs

RescueTime is a time-tracking and productivity service that measures how time is spent across applications, websites, and offline activities. Its APIs expose that recorded data as analytic feeds and daily summaries, along with operations for logging highlights, posting offline time, and starting or ending FocusTime sessions. Both APIs cover the same RescueTime account data, so an agent can read productivity metrics and write focus and highlight events against a single connected account.

## For AI agents

An agent can read RescueTime activity and productivity data, pull daily summary, alerts, highlights, and focus-session feeds, and write back highlights, offline time entries, and FocusTime start or end events across the vendor's two analytic APIs.

## Scope

Use for: Reading RescueTime time-tracking and productivity data, pulling daily summary, alerts, and highlight feeds, and logging highlights, offline time, and FocusTime sessions for a connected account

Not supported:
- payment processing
- team messaging
- crm records
- calendar scheduling
- real-time streaming

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| RescueTime API | analytics | 12 | Programmatically retrieve analytic data, retrieve daily summary feed. |
| RescueTime Analytic Data API | identity-auth | 8 | Programmatically get analytic data, daily summary feed. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Read analytic data plus manage FocusTime sessions with explicit start and end | rescuetime-api | This API exposes both start and end focus-session operations and a focus-session start events feed, so an agent can open and close a session and observe start events. |
| Read analytic data and log offline time | rescuetime | This API adds a post offline time operation for recording activity that happened away from tracked devices, which the other API does not expose. |

## Cross-API use cases

### Daily productivity report with focus context

Pull the daily summary and analytic data to build a productivity report, then read the focus-session feed to annotate which blocks were tracked focus time.

Example prompt: Call the daily summary and analytic data endpoints, then read the focus-session feed and combine both into a report.

### Log a focus block and record its offline follow-up

Start a FocusTime session through one API, then use the other to post offline time for work done away from the device during the same period.

Example prompt: Start a FocusTime session on one API and post an offline time entry on the other for the same interval.

### Highlight and alert digest

Read the alerts and highlights feeds for the account and post new highlights to record notable events, using whichever API exposes the needed write path.

Example prompt: Read the alerts and highlights feeds, then post a new highlight summarizing the period.

## Why Jentic

- **Setup:** Wiring RescueTime by hand means choosing between its query-string API key and the OAuth2 authorization-code flow and constructing feed calls against the www.rescuetime.com host for each API. With Jentic One installed, your agent finds and adds either RescueTime API from the Jentic directory and stores the credential once.
- **Permission scoping:** Both APIs address their data through operations rather than resource ids in the path, so you scope the agent to the operations it should use. Read feeds such as daily summary or analytic data can be allowed while write operations like posting offline time or starting FocusTime stay out unless you add them, using your own rules in your Jentic One instance.
- **Credential handling:** Your RescueTime API key or OAuth credentials are stored once, encrypted, in your own Jentic One instance and injected at execution time. Because one credential covers both APIs, it is entered once and never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search the Jentic directory by intent, such as retrieving analytic data or starting a focus session, and Jentic returns the matching RescueTime operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related vendors

- **Toggl** — Time-tracking service with an API for logging and reporting time entries, an alternative source of productivity data.
- **Clockify** — Time-tracking API covering entries and reports, adjacent for teams comparing productivity tooling.
- **Mixpanel** — Product analytics API for event and behavior data, complementary when combining usage analytics with time tracking.

## FAQ

### What can an agent do across the RescueTime APIs?

An agent can read time-tracking and productivity data, pull daily summary, alerts, highlights, and focus-session feeds, and write highlights, offline time, and FocusTime start or end events. Together the two APIs cover both reading recorded activity and logging new events.

### Do the two RescueTime APIs cover the same data?

Yes. Both read from the same RescueTime account and expose overlapping analytic feeds and daily summaries. They differ mainly in endpoint paths and which write operations they include, so the choice usually comes down to whether you need offline-time posting or explicit focus-session start and end.

### Do I need separate credentials for each API?

No. Both APIs use the same API key or OAuth2 credentials against the same account, so one credential covers both. When connected through Jentic, that credential is stored once in your own Jentic One instance.

### How fresh is the data these APIs return?

RescueTime syncs activity data roughly every 3 minutes on paid plans and every 30 minutes on the free Lite plan, so feed responses reflect near-recent activity rather than a live stream. Plan behavior is set by RescueTime, not by the API.

### Which API should an agent choose for focus tracking?

Use the RescueTime API when you need to both start and end a focus session and read focus start events. Use the Analytic Data API when you additionally need to post offline time. Both read analytic data, so overlap on read operations is expected.

### What are these APIs not suited for?

They cover time-tracking analytics and focus logging only. They do not handle payments, messaging, CRM records, or calendar scheduling. Despite one being tagged under authentication, neither is an identity provider; both operate on RescueTime productivity data.