Vimeo

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

Detail	Value
Category	Media
Base URL	https://api.vimeo.com
Authentication	Bearer Token
Endpoints	6
Connector key	vimeo

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

Endpoint	Summary
GET /me	Get authenticated user info
GET /me/videos	List 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 /videos	Search 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

Detail	Value
Operation ID	media.getUser
Method	GET
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

Detail	Value
Operation ID	media.listMyVideos
Method	GET
Path	/me/videos

Parameters

Name	Location	Type	Required
per_page	query	integer	No
page	query	integer	No

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

Detail	Value
Operation ID	media.getVideo
Method	GET
Path	/videos/{video_id}

Parameters

Name	Location	Type	Required
video_id	path	string	Yes

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

Detail	Value
Operation ID	media.deleteVideo
Method	DELETE
Path	/videos/{video_id}

Parameters

Name	Location	Type	Required
video_id	path	string	Yes

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

Detail	Value
Operation ID	media.updateVideo
Method	PATCH
Path	/videos/{video_id}

Parameters

Name	Location	Type	Required
video_id	path	string	Yes

Request Body

Field	Type
name	string
description	string

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

Detail	Value
Operation ID	media.searchVideos
Method	GET
Path	/videos

Parameters

Name	Location	Type	Required
query	query	string	Yes
per_page	query	integer	No

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.