canonical: https://jentic.com/apis/sonix.ai/sonix-api

# Sonix API

API for automated transcription, translation, and subtitle creation for audio and video files. The API exposes 23 endpoints secured with bearer authentication.

## For AI agents

Programmatically submit new media, list media files. Covers 23 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Submit new media
- List media files
- Get media status
- Update media
- Delete media

## Use cases

### AI and Machine Learning Operations

Use the Sonix API to perform ai ml operations programmatically. The API provides 23 endpoints covering core functionality including submit new media, list media files, get media status.

Example prompt: Call POST /media to submit new media

### Automated folders Management

Automate folders operations by combining multiple Sonix API endpoints. Agents can list media files and then get media status in a single workflow.

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

### AI Agent Integration via Jentic

AI agents discover and call Sonix 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 bearer tokens manually.

Example prompt: Search Jentic for 'submit new media', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/media` | Submit new media |
| GET | `/media` | List media files |
| GET | `/media/{id}` | Get media status |
| PUT | `/media/{id}` | Update media |
| DELETE | `/media/{id}` | Delete media |
| GET | `/media/{id}/transcript` | Get transcript |
| PUT | `/media/{id}/transcript` | Update transcript |
| PUT | `/media/{id}/transcript/split` | Split transcript into subtitles |

## Key resources

- **folders** — Operations related to folders
- **media** — Operations related to media
- **summarizations** — Operations related to summarizations
- **users** — Operations related to users
- **video_burn_ins** — Operations related to video_burn_ins

## Why Jentic

- **Setup:** Wiring the Sonix API by hand means setting up its bearer auth, pointing at the api.sonix.ai/v1 host, and handling media upload and transcript editing plus retries yourself. Through Jentic you install once, import the Sonix API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** The Sonix API puts the media id in the URL path (`/media/{id}`, `/media/{id}/transcript/split`), so a rule can pin your agent to one media file: it can read and edit that file's transcript and nothing else. You choose the operations it may call, so destructive ones like deleting media are not included unless you add them.
- **Credential handling:** Your Sonix token 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 'submit new media' or 'edit a transcript', and Jentic returns the matching Sonix API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the Sonix API use?

The Sonix API uses a Bearer token in the Authorization 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 submit new media with the Sonix API?

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

### What are the rate limits for the Sonix 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 submit new media through Jentic?

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

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

The Sonix API exposes 23 endpoints covering folders, media, summarizations operations.

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

Yes. Because Jentic One runs self-hosted on your own infrastructure, you write the rules that decide which Sonix API operations and credentials the agent may use. Since the Sonix API carries the media id in the URL path (for example `/media/{id}` and `/media/{id}/transcript/split`), a rule can pin the agent to a single media file so it only reads and edits that file's transcript and nothing else. You also choose the exact operations it may call, so destructive ones such as DELETE `/media/{id}` stay out of reach unless you explicitly grant them.