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

# Voomly API

Video hosting and analytics platform API for managing videos, players, and viewing analytics. The API exposes 14 endpoints secured with apiKey authentication.

## For AI agents

Programmatically upload video, list videos. Covers 14 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Upload video
- List videos
- Get video
- Update video
- Delete video
- Create player

## Use cases

### Cloud Infrastructure Operations

Use the Voomly API to perform cloud infrastructure operations programmatically. The API provides 14 endpoints covering core functionality including upload video, list videos, get video.

Example prompt: Call POST /videos to upload video

### Automated Videos Management

Automate videos operations by combining multiple Voomly API endpoints. Agents can list videos and then get video in a single workflow.

Example prompt: Call GET /videos to list videos, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Voomly API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'upload video', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/videos` | Upload video |
| GET | `/videos` | List videos |
| GET | `/videos/{videoId}` | Get video |
| PUT | `/videos/{videoId}` | Update video |
| DELETE | `/videos/{videoId}` | Delete video |
| GET | `/videos/{videoId}/analytics` | Get video analytics |
| POST | `/players` | Create player |
| GET | `/players` | List players |

## Key resources

- **Videos** — Video management
- **Players** — Video player management
- **Analytics** — Video analytics and statistics
- **Projects** — Project management

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 60 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/voomly.com/voomly/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Voomly by hand means setting its X-API-Key header against api.voomly.com and managing the video and player calls yourself. Through Jentic you install once, import Voomly from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Voomly puts the video id in the URL path (`/videos/{videoId}`), so a rule can pin your agent to reading one video and its analytics. You choose the operations it may call, so destructive ones like video deletion are not included unless you add them.
- **Credential handling:** Your Voomly API key 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 'upload a video' or 'read video analytics', and Jentic returns the matching Voomly operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the Voomly API use?

The Voomly API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I upload video with the Voomly API?

Yes. Use the POST /videos endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I upload video through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'upload video'. Jentic returns the matching Voomly API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Voomly API have?

The Voomly API exposes 14 endpoints covering videos, players, analytics operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Voomly operations and credentials the agent may use. Since Voomly puts the video id in the URL path (`/videos/{videoId}`), you can pin the agent to reading a single video and its analytics through GET `/videos/{videoId}` and GET `/videos/{videoId}/analytics.` You choose the operations it may call, so destructive actions like DELETE `/videos/{videoId}` stay off limits unless you explicitly add them.