canonical: https://jentic.com/apis/swaggerhub.5centscdninc/5centscdn---transcoding

# 5centscdninc 5centsCDN - Transcoding

API for managing Transcoding in <a href="https://www.5centscdn.net" target="_blank">5centsCDN</a>. The API exposes 15 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list active video encoding jobs, list active video encoding jobs by zoneid. Covers 15 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for hr and recruiting only.

## Capabilities

- List Active Video Encoding Jobs
- Add Video Encoding Jobs
- Retry enoding job
- Cancel Enoding Job
- Create Global Auto Transcode Preset Profiles

## Use cases

### HR and Recruiting Operations

Use the 5centsCDN - Transcoding to perform hr recruiting operations programmatically. The API provides 15 endpoints covering core functionality including list active video encoding jobs, list active video encoding jobs by zoneid, add video encoding jobs.

Example prompt: Call GET /transcoding/jobs to list active video encoding jobs

### Automated Video Encoding Jobs Management

Automate video encoding jobs operations by combining multiple 5centsCDN - Transcoding endpoints. Agents can list active video encoding jobs by zoneid and then add video encoding jobs in a single workflow.

Example prompt: Call POST /transcoding/jobs/{zoneid} to list active video encoding jobs by zoneid, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call 5centsCDN - Transcoding 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 'list active video encoding jobs', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /transcoding/jobs | List Active Video Encoding Jobs |
| POST | /transcoding/jobs/{zoneid} | List Active Video Encoding Jobs by ZoneID |
| POST | /transcoding/jobs/{zoneid}/{profileid} | Add Video Encoding Jobs |
| GET | /transcoding/jobs/retry/{jobid} | Retry enoding job |
| GET | /transcoding/jobs/cancel/{jobid} | Cancel Enoding Job |
| GET | /transcoding/file/profiles | List File Transcoding Profiles |
| POST | /transcoding/file/profiles/defaults | Create Global Auto Transcode Preset Profiles |
| POST | /transcoding/file/profiles/new | Create Transcoding Profiles |

## Key resources

- **Video Encoding Jobs** — endpoints related to manage Video Encoding
- **File Transcoding Profiles** — endpoints related to Global Transcode Preset Profiles
- **Reports -  Video Encoding Minutes** — Reports for  Video Transcoding Minutes

## Why Jentic

- **Setup:** Wiring the 5centsCDN Transcoding API by hand means attaching its X-API-Key header to every request against api.5centscdn.com and tracking encoding jobs and profiles yourself. Through Jentic you install once, import the 5centsCDN Transcoding API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** 5centsCDN puts the zone, profile, and job id in the URL path (/transcoding/jobs/{zoneid}, /transcoding/jobs/{zoneid}/{profileid}, /transcoding/jobs/cancel/{jobid}), so a rule can pin your agent to one zone or job. You choose the operations it may call, so a job control like cancelling a job is not included unless you add it.
- **Credential handling:** Your 5centsCDN 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 'list transcoding jobs' or 'create a transcoding profile', and Jentic returns the matching 5centsCDN Transcoding operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Greenhouse** — Alternative hr recruiting API
- **Lever** — Alternative hr recruiting API
- **Workday** — Complementary hr recruiting API

## FAQ

### What authentication does the 5centsCDN - Transcoding use?

The 5centsCDN - Transcoding 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 list active video encoding jobs with the 5centsCDN - Transcoding?

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

### What are the rate limits for the 5centsCDN - Transcoding?

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 list active video encoding jobs through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list active video encoding jobs'. Jentic returns the matching 5centsCDN - Transcoding operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the 5centsCDN - Transcoding have?

The 5centsCDN - Transcoding exposes 15 endpoints covering video encoding jobs, file transcoding profiles, reports -  video encoding minutes operations.

### Can I limit what my agent is allowed to do with the 5centsCDN Transcoding API?

Yes. Because you run Jentic One yourself, your own rules decide which 5centsCDN Transcoding operations and credentials the agent may use. Since 5centsCDN puts the zone, profile, and job id in the URL path (/transcoding/jobs/{zoneid}, /transcoding/jobs/{zoneid}/{profileid}, /transcoding/jobs/cancel/{jobid}), you can pin the agent to a single zone or job. You also choose the operations it may call, so a control such as cancelling an encoding job stays out of reach unless you explicitly grant it.
