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

# Loom API

Loom is an asynchronous video messaging platform whose API exposes recording, video, folder, and usage operations for workspaces. The 7 endpoints cover listing, retrieving, updating, and deleting recorded videos, listing folders, generating one-time recording links to embed in third-party tools, and reporting account usage. Authentication uses a bearer token issued from the workspace settings.

## For AI agents

Manage Loom video recordings - list, fetch, update, and delete videos, generate recording links, and read workspace usage stats - via 7 endpoints behind a bearer token.

## Scope

Does not handle live video meetings, transcript generation, or in-app video playback controls - use for Loom workspace video, folder, recording-link, and usage operations only.

## Capabilities

- List and filter recorded videos within a Loom workspace by folder or owner
- Retrieve a single video's metadata including title, owner, share URL, and duration
- Update a video's title, description, or folder placement after recording
- Delete videos from the workspace when retention policy requires it
- Generate a one-time recording link that lets an external user record into the workspace
- Pull workspace usage statistics for licence-management or billing reconciliation

## Use cases

### Async candidate interview workflow

Recruiting platforms generate a Loom recording link for each candidate, send it in a templated email, and ingest the resulting video back into the candidate profile. The /record-link endpoint returns a one-time URL so candidates do not need a Loom account, and the GET `/videos/{id}` call retrieves the resulting recording for review by the hiring panel. Setup takes under a day once the bearer token is in place.

Example prompt: Create a recording link via POST /record-link, store the returned URL on candidate 12345's profile, and after the candidate records, fetch the resulting video metadata with GET `/videos/{id}.`

### Video library hygiene

Internal-comms teams use the Loom API to enforce retention rules - list videos older than a threshold, delete the ones outside policy, and move active recordings into the right folder. With only 7 endpoints, the full lifecycle (list, get, update, delete) fits in a single scheduled job that runs against an entire workspace.

Example prompt: List videos via GET /videos, filter to recordings created over 180 days ago, and DELETE `/videos/{id}` for each one while logging the result.

### Sales engagement video tracking

Sales tools use the Loom API to attach recorded videos to CRM contacts, then poll usage stats to understand reach and license utilisation across reps. The GET `/videos/{id}` response includes the share URL that the CRM stores, while GET /usage gives finance the headcount of active recorders for licence true-up.

Example prompt: For each recently recorded video, fetch metadata with GET `/videos/{id}`, attach the share URL to the matching CRM contact, and append a daily snapshot of GET /usage to the finance dashboard.

### Agent-driven video summary via Jentic

An AI agent watches a project channel for new Loom shares, fetches each video's metadata through Jentic, and posts a concise summary plus the share link back to the channel. Jentic isolates the bearer token in the credential vault so the agent never holds the raw secret, and the small surface area (7 endpoints) means the operation list loads in one search.

Example prompt: Use Jentic to search 'get loom video metadata', load GET `/videos/{id}`, execute it with the video ID parsed from the chat link, and return title, duration, and share URL to the agent.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/videos` | List videos in the workspace |
| GET | `/videos/{id}` | Get a single video's metadata |
| PATCH | `/videos/{id}` | Update a video's title, description, or folder |
| DELETE | `/videos/{id}` | Delete a video from the workspace |
| GET | `/folders` | List folders in the workspace |
| POST | `/record-link` | Create a one-time recording link |
| GET | `/usage` | Get workspace usage stats |

## Key resources

- **Videos** — List, fetch, update, and delete recorded videos with their share URLs and metadata
- **Folders** — List the folders that organise videos within a workspace
- **Recording** — Generate one-time recording links to invite external recorders
- **Usage** — Read workspace usage statistics for licence and billing reconciliation

## Why Jentic

- **Setup:** Wiring the Loom API by hand means setting up its workspace bearer auth, attaching the token to every call against api.loom.com, and shaping video, folder, and record-link requests yourself. Through Jentic you install once, import Loom from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Loom puts the video id in the URL path (`/videos/{id}`), so a rule can pin your agent to one video: it can read and update that video and nothing else. You choose the operations it may call, so destructive ones like deleting a video are not included unless you add them.
- **Credential handling:** Your Loom workspace bearer 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 'create a Loom recording link' or 'list Loom videos', and Jentic returns the matching Loom operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Vimeo API** — Hosted video platform with broader transcoding, privacy, and embed controls than Loom
- **Zoom Meetings API** — Synchronous video meetings with cloud recording rather than async screen recordings
- **Calendly API** — Scheduling API for booking the meetings that often follow an async Loom share
- **HubSpot Account Info API** — CRM platform that stores contact records to which Loom share URLs can be attached

## FAQ

### What authentication does the Loom API use?

The Loom API uses bearer-token authentication - generate a workspace API token in Loom's developer settings and send it in the Authorization header. Through Jentic, the token is stored encrypted in the vault and the agent receives a scoped access reference rather than the raw bearer string.

### Can I generate a Loom recording link for someone outside my workspace?

Yes. POST /record-link creates a one-time recording URL that an external user can open in a browser to record straight into your workspace. Use Jentic search 'create loom recording link' to load and execute the operation.

### What are the rate limits for the Loom API?

Loom does not publish a fixed numeric limit; the API will return HTTP 429 when traffic is throttled. Jentic surfaces 429 responses to the agent so it can back off and retry, and the small endpoint count (7) makes per-resource quotas straightforward to track.

### How do I delete an old Loom video through Jentic?

Search Jentic for 'delete loom video', load the DELETE `/videos/{id}` operation, and execute it with the video ID. Jentic injects the bearer token automatically, so the agent only supplies the ID it wants removed.

### Does the Loom API support transcripts or AI summaries?

The public API exposes video metadata, recording links, and usage - not transcript text or AI summary output. For workflows that need transcripts, retrieve the share URL via GET `/videos/{id}` and pair it with a separate transcription service.

### How many endpoints does the Loom API expose?

Seven: list and get videos, update and delete videos, list folders, create a recording link, and get workspace usage. The full surface area fits in a single Jentic operation search rather than tag-by-tag browsing.

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

Yes. Because you run Jentic One yourself, your own rules decide which of Loom's operations the agent may call, so you can grant read-only access with GET /videos and GET `/videos/{id}` while withholding PATCH `/videos/{id}` and the DELETE `/videos/{id}` operation entirely. Since the video id sits in the URL path, a rule can pin the agent to a single video, letting it read or update that one recording and nothing else. Destructive calls like deleting a video are excluded unless you add them, and the workspace bearer token stays with your instance rather than in the agent's context.