Loom API

Name: Loom API API
Brand: Loom API
Availability: InStock

✓ Official Vendor SpecMediaVideo Processingbearer7 EndpointsREST

For 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.

Quickstart

Get started with Loom API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"create a loom recording link"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Loom API API.

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

GET STARTED

Start building with Loom API API

Explore with Jentic

View OpenAPI Document

Use for: I need to list all Loom videos in a workspace, Get the share URL and duration for a specific Loom video, Update the title of a Loom recording, Delete a Loom video that is older than 90 days

Not supported: 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.

Use Cases

Patterns agents use Loom API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

7 endpoints — loom is an asynchronous video messaging platform whose api exposes recording, video, folder, and usage operations for workspaces.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Loom workspace bearer tokens are stored encrypted in the Jentic vault. Agents call operations with a scoped reference — the raw bearer string never enters the agent's context, which matters because Loom tokens are workspace-wide.

Intent-based discovery

Agents search by intent (for example 'create loom recording link' or 'list loom videos') and Jentic returns the matching Loom operation with its input schema, so the agent does not need to consult the developer portal.

Time to first call

Direct Loom integration: half a day for token issuance, error handling, and 429 backoff. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Vimeo API

Hosted video platform with broader transcoding, privacy, and embed controls than Loom

Choose Vimeo when the workflow needs published-quality marketing or product video; choose Loom for async screen-and-camera recordings inside a workspace.

Alternative

Zoom Meetings API

Synchronous video meetings with cloud recording rather than async screen recordings

Use Zoom for live meetings that should be recorded centrally; use Loom when the moment is asynchronous and the recording is the primary artefact.

Complementary

Calendly API

Scheduling API for booking the meetings that often follow an async Loom share

Pair Calendly with Loom when an async Loom is sent first and a follow-up live meeting needs to be booked once the recipient responds.

Complementary

HubSpot Account Info API

CRM platform that stores contact records to which Loom share URLs can be attached

Use HubSpot alongside Loom when sales-engagement videos should be logged on the contact timeline next to other touchpoints.

FAQs

Specific to using Loom API API through Jentic.

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.