Skip to content
For LLMsView as Markdown·

Vimeo ​

Upload, manage, and stream videos with the Vimeo API. Access user data, video analytics, and player customization.

DetailValue
CategoryMedia
Base URLhttps://api.vimeo.com
AuthenticationBearer Token
Endpoints6
Connector keyvimeo

Using Vimeo in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Vimeo from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET /meGet authenticated user info
GET /me/videosList videos for the authenticated user
GET /videos/{video_id}Get a video by ID
DELETE /videos/{video_id}Delete a video
PATCH /videos/{video_id}Edit video metadata
GET /videosSearch for videos

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /me ​

Get authenticated user info

DetailValue
Operation IDmedia.getUser
MethodGET
Path/me

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Vimeo connection from the Connection dropdown.
  3. In the Operation dropdown, select media.getUser.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vimeo API reference.

GET /me/videos ​

List videos for the authenticated user

DetailValue
Operation IDmedia.listMyVideos
MethodGET
Path/me/videos

Parameters ​

NameLocationTypeRequired
per_pagequeryintegerNo
pagequeryintegerNo

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Vimeo connection from the Connection dropdown.
  3. In the Operation dropdown, select media.listMyVideos.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vimeo API reference.

GET /videos/{video_id} ​

Get a video by ID

DetailValue
Operation IDmedia.getVideo
MethodGET
Path/videos/{video_id}

Parameters ​

NameLocationTypeRequired
video_idpathstringYes

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Vimeo connection from the Connection dropdown.
  3. In the Operation dropdown, select media.getVideo.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vimeo API reference.

DELETE /videos/{video_id} ​

Delete a video

DetailValue
Operation IDmedia.deleteVideo
MethodDELETE
Path/videos/{video_id}

Parameters ​

NameLocationTypeRequired
video_idpathstringYes

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Vimeo connection from the Connection dropdown.
  3. In the Operation dropdown, select media.deleteVideo.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vimeo API reference.

PATCH /videos/{video_id} ​

Edit video metadata

DetailValue
Operation IDmedia.updateVideo
MethodPATCH
Path/videos/{video_id}

Parameters ​

NameLocationTypeRequired
video_idpathstringYes

Request Body ​

FieldType
namestring
descriptionstring

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Vimeo connection from the Connection dropdown.
  3. In the Operation dropdown, select media.updateVideo.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vimeo API reference.

GET /videos ​

Search for videos

DetailValue
Operation IDmedia.searchVideos
MethodGET
Path/videos

Parameters ​

NameLocationTypeRequired
queryquerystringYes
per_pagequeryintegerNo

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Vimeo connection from the Connection dropdown.
  3. In the Operation dropdown, select media.searchVideos.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

Required fields are marked: fill them or the call will fail at runtime.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Vimeo API reference.