# tl;dv

> Read tl;dv meeting recordings - meetings, transcripts, highlights, AI notes - via the REST API.

Lets an agent read your tl;dv meeting data through the REST API (currently `v1alpha1`): list and get meetings, fetch the transcript, highlights, and AI notes. Useful for pulling meeting context and follow-ups into a workflow.

## What it can do

| Method | What it does |
| --- | --- |
| `tldv_meetings_list` | List meetings (filter by query, date range, type, participation). |
| `tldv_meeting_get` | Get one meeting's details by ID. |
| `tldv_transcript_get` | Get the transcript for a meeting. |
| `tldv_highlights_get` | Get the highlights for a meeting. |
| `tldv_notes_get` | Get the AI notes for a meeting. |
| `tldv_request` | Generic passthrough to any endpoint for full API coverage. |

## How to get your API key

tl;dv authenticates with an **API key** sent as the `x-api-key` header.

1. Sign in to tl;dv.
2. Open **Settings -> Developer / API** ([tldv.io/app/settings/developers](https://tldv.io/app/settings/developers)).
3. Generate an API key and copy it.
4. Paste it into FlyMyAI.

## Fields to fill

| FlyMyAI field | Where it comes from |
| --- | --- |
| `TLDV_API_KEY` | tl;dv -> Settings -> Developer / API |

## Troubleshooting

- **`401 Unauthorized`** - the key is wrong or revoked. Generate a new one under Settings -> Developer / API.
- **`403 Forbidden`** - your tl;dv plan does not include API access; the developer API requires a paid plan.
- **`404 Not Found`** - the meeting ID is wrong; list meetings first with `tldv_meetings_list`.
- **API shape changes** - the API is in `v1alpha1` and may change before the stable release. If a named action breaks, use `tldv_request` with the current path.

## Links

- [tl;dv API documentation](https://doc.tldv.io)
- [Developer settings](https://tldv.io/app/settings/developers)