> ## Documentation Index
> Fetch the complete documentation index at: https://onecli.sh/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Timeless Integration: Meeting Recordings and Transcripts for Agents

> Agents can read meetings, transcripts, and AI summaries in Timeless, and send the note-taker bot to calls. Connect with an API token.

## Overview

OneCLI connects AI agents to [Timeless](https://timeless.day) with an API token. Agents can search meetings, read transcripts and summaries, and send the note-taker to a call. The gateway injects the token into requests to `api.timeless.day`, so your agent never sees it.

This suits agents that turn calls into follow-ups: drafting recaps, filing action items into a tracker, or answering "what did we agree with this customer last week?"

Timeless has no OAuth for its public API, so an API token is the only connection method.

## Setup

Timeless needs one field, an API token. The whole flow takes about a minute.

<Steps>
  <Step title="Generate an API token in Timeless">
    Sign in to Timeless and open [my.timeless.day/api-token](https://my.timeless.day/api-token). Create a token and copy it.

    Tokens are 64-character hex strings and carry the same access as your Timeless account, so treat the token like a password.
  </Step>

  <Step title="Connect in OneCLI">
    In the OneCLI dashboard, open **Connections** > **Timeless** and paste the token into **API token**. Under **Advanced** you can set an optional connection label to tell several Timeless accounts apart, for example `work` or `personal`.

    <Frame caption="The Timeless connect dialog in OneCLI.">
      <img src="https://mintcdn.com/chartdbinc/i1gAOGaIZu_91FII/images/integrations/timeless/onecli-connect-timeless.png?fit=max&auto=format&n=i1gAOGaIZu_91FII&q=85&s=81d824e6865d943b13a3a3a9c0258e55" alt="OneCLI connect dialog for Timeless, showing the required API token field, a Get your API token link, an Advanced section with an optional connection label, and the Connect Timeless button." width="1280" height="1300" data-path="images/integrations/timeless/onecli-connect-timeless.png" />
    </Frame>

    Click **Connect Timeless**. OneCLI verifies the token against the Timeless API and rejects it if Timeless returns a `401`.
  </Step>
</Steps>

## What agents can do

| Area | Description |
| - | - |
| **Meetings** | List recorded meetings, filtered by status, date, participant, company, or room. Includes semantic search over meeting content, not just titles |
| **Upcoming meetings** | Read scheduled events from the connected calendar, with their join links |
| **Transcripts** | Fetch time-stamped transcripts with speaker identification |
| **Recordings** | Get a short-lived download URL for a meeting recording |
| **Documents** | Read AI-generated summaries, action items, and notes as Markdown, HTML, plain text, JSON, or `.docx` |
| **Note-taker bot** | Schedule the bot for a calendar event, send it to a call link, or cancel it |
| **Automation settings** | Read and change when the note-taker joins meetings on its own |
| **Rooms** | List rooms, which group related meetings |
| **Sharing** | List, grant, and revoke per-meeting permissions |
| **Webhooks** | Create, list, update, and delete webhook subscriptions |
| **Upload** | Upload an audio or video file for transcription |

A token inherits your own Timeless access, so an agent reaches the meetings you can reach, and no more.

## Quick example

No `Authorization` header is needed, the gateway adds it:

```bash theme={null}
# Ten most recent meetings
curl -s "https://api.timeless.day/v1/meetings?limit=10"

# Pull a transcript with speaker labels
curl -s "https://api.timeless.day/v1/meetings/mtg_abc123/transcript"

# Include AI-generated documents inline instead of a second request
curl -s "https://api.timeless.day/v1/meetings?expand=documents"
```

For filters, pagination, and response shapes, see the [Timeless API reference](https://docs.timeless.day/api-reference/introduction).

## Disconnecting

* In OneCLI, open **Connections** > **Timeless** and remove the connection.
* In Timeless, delete the token at [my.timeless.day/api-token](https://my.timeless.day/api-token).

Removing the connection in OneCLI stops injection immediately. Deleting the token in Timeless is what actually revokes it, so do both.

## Controlling access

Access is per agent: [grant](/docs/guides/agent-access) the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked.

Meeting content is sensitive, and some Timeless calls are not read-only. Sending the note-taker bot into a live call, changing automation settings, and granting public share links all have real-world effects, so those are worth putting behind approval while leaving reads free. Organization [rules](/docs/guides/rules) add guardrails on top, like rate limits. Everything is checked before credential injection, so a blocked request never reaches Timeless.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.