[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create clip

> Save a segment of a meeting as a clip in your Clips library. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/tldv/create_clip

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Save a segment of a meeting as a clip in your Clips library.

tl;dv API: https://cotlet.dev/docs/api/tldv.md

`POST https://cotlet.dev/api/v1/tldv/meetings/{meeting_id}/clips`

Access: write.

Cuts a clip from a start and an end time of one meeting, the same as Create clip on the recording, and saves it in your Clips library under the title you give. The call returns the clip ID and its link, and nothing is shared: tl;dv lets anyone who gets a clip link view it, so you decide where the link goes. It reaches no one, so it runs without asking first.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `meeting_id` | string | yes | Meeting ID from list_meetings. |
| `from_time` | string | yes | Start of the segment, hh:mm:ss. |
| `to_time` | string | yes | End of the segment, hh:mm:ss. |
| `title` | string | no | Clip title. Default: the meeting title. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/tldv/meetings/mt_4f21a9/clips \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"from_time":"00:12:05","to_time":"00:12:53","title":"Budget confirmed for Q4"}'
```

**Python**

```python
result = client.call("tldv", "create_clip", {"meeting_id":"mt_4f21a9","from_time":"00:12:05","to_time":"00:12:53","title":"Budget confirmed for Q4"})
```

**Node.js**

```js
const result = await cotlet.call('tldv', 'create_clip', {"meeting_id":"mt_4f21a9","from_time":"00:12:05","to_time":"00:12:53","title":"Budget confirmed for Q4"});
```

**CLI**

```bash
cotlet call tldv create_clip --data '{"meeting_id":"mt_4f21a9","from_time":"00:12:05","to_time":"00:12:53","title":"Budget confirmed for Q4"}'
```

## Example response

```json
{
  "clip_id": "cl_71d0",
  "meeting_id": "mt_4f21a9",
  "title": "Budget confirmed for Q4",
  "from_time": "00:12:05",
  "to_time": "00:12:53",
  "duration_seconds": 48,
  "url": "https://tldv.io/app/clips/cl_71d0"
}
```

Previous: [Add note](https://cotlet.dev/docs/api/tldv/add_note.md)
Next: [Rename meeting](https://cotlet.dev/docs/api/tldv/rename_meeting.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.