# Vidyard integrations: videos, players and captions

> Create a video, create a player and create a caption in Vidyard, and start a workflow when Vidyard sends “Video viewed”.

**Canonical page:** https://tray.ai/connectors/vidyard-integrations/
**Categories:** Marketing
**Connects through:** HTTP Connector

## Overview

Vidyard is a video platform for sales and marketing teams to record, host and share videos, with embeddable players, video hubs and viewer analytics. Tray.ai connects to Vidyard through the HTTP Connector, so your workflows can call the Vidyard API alongside the rest of your stack.

## Use cases

### Videos

Read and create videos in Vidyard from any Tray.ai workflow. The Vidyard API covers calls such as create a video and get a video.

- Create a video
- Get a video
- List videos

### Players

Read, create, update, and delete players in Vidyard from any Tray.ai workflow. The Vidyard API covers calls such as create a player and get a player.

- Create a player
- Get a player
- Update a player

### Captions

Read, create, update, and delete captions in Vidyard from any Tray.ai workflow. The Vidyard API covers calls such as list captions and create a caption.

- List captions
- Create a caption
- Update a caption

### Tags

Read, create, update, and delete tags in Vidyard from any Tray.ai workflow. The Vidyard API covers calls such as list tags and create a tag.

- List tags
- Create a tag
- Update player tags

### Events

Read, create, update, and delete events in Vidyard from any Tray.ai workflow. The Vidyard API covers calls such as list events and create an event.

- List events
- Create an event
- Update an event

### Webhooks

Delete webhooks in Vidyard from any Tray.ai workflow. The Vidyard API covers calls such as register an analytics webhook and register a player webhook.

- Register an analytics webhook
- Register a player webhook
- Delete a webhook

## Challenges Tray.ai solves

### Keeping Vidyard credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Vidyard credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Vidyard API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Vidyard API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Vidyard?

Yes. Tray.ai connects to Vidyard through the HTTP Connector, which calls the Vidyard API directly. Any call the Vidyard API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Vidyard?

The Vidyard API uses an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Vidyard connector?

Vidyard runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Vidyard connector from the Vidyard API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/