ContentGroove API

Name: ContentGroove API API
Brand: ContentGroove API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo ProcessingapiKey15 EndpointsREST

For Agents

Upload video or audio, run ContentGroove's AI to transcribe and extract suggested clips, and receive webhook callbacks when processing completes.

Quickstart

Get started with ContentGroove API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"generate video clips with contentgroove"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with ContentGroove API API.

Ingest video or audio from a source URL or via direct upload up to 5 GB

Trigger automatic transcription, topic extraction, and keyword detection on uploaded media

Read suggested AI-generated video clips along with manually created clips

Define custom video clip ranges over an existing media

GET STARTED

Start building with ContentGroove API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for ContentGroove API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for ContentGroove API, keeping it validated and agent-ready. ContentGroove ingests video and audio media, runs AI processing for transcription, topic and keyword extraction, and suggested clips, and exposes the results through 15 endpoints across media, clips, direct uploads, and webhook subscriptions. Authentication uses an API key passed as Authorization Bearer, X-API-KEY header, or api_key query parameter, and webhook callbacks notify external systems when a media has finished processing.

Use Cases

Patterns agents use ContentGroove API API for, with concrete tasks.

★ Podcast and Webinar Repurposing

Marketing teams upload long-form podcast episodes or webinar recordings and use ContentGroove's AI to surface suggested short clips, transcripts, and topic tags. The clips and transcript can be pulled back into a CMS or social-media scheduler so editors review rather than create from scratch. Typical processing time scales with media duration, and webhook callbacks remove the need to poll.

POST a media to /api/v1/medias with source_url pointing to a 60-minute podcast MP3, register a webhook on /api/v1/webhook_subscriptions, and on callback retrieve the suggested clips list

Searchable Video Library

Education and training platforms ingest course videos, attach transcripts, and expose keywords and topics so students can search inside videos rather than scrubbing manually. ContentGroove returns transcript text, keyword lists, and topic groupings tied to the media id, which a downstream search index can pick up. Webhook callbacks make ingestion event-driven instead of poll-driven.

Upload a course video via direct upload, wait for the processing-complete webhook, and store the returned transcript, topics, and keywords in a search index

Direct Upload Workflow for Large Files

When source media is not reachable by URL, applications use the direct upload flow: GET /api/v1/direct_uploads to obtain a signed upload URL and upload id, PUT the file to the signed URL, then POST /api/v1/medias with the upload id. This keeps large files (up to 5 GB) off the application server and avoids streaming through middleware. Direct uploads are the recommended path for user-generated content from a browser or mobile client.

Call GET /api/v1/direct_uploads, PUT a 2 GB MP4 to the returned URL, then POST /api/v1/medias with the upload id and a name

AI Agent Video Clip Generator via Jentic

An AI agent embedded in a content production tool uses Jentic to upload a recording, wait for processing, and return a list of clip suggestions ranked by topic relevance. Jentic stores the ContentGroove API key in the MAXsystem vault and signs each call with a scoped token. Webhook delivery URLs are still owned by the application; Jentic only proxies the API calls the agent makes.

Search Jentic for 'create a contentgroove media', execute with source_url, poll /api/v1/medias/{id} until state is processed, and return the suggested clips

Key Endpoints

15 endpoints — jentic publishes the only available openapi specification for contentgroove api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/api/v1/medias

Create a new media from a source URL or upload id

GET

/api/v1/medias

List medias in the account

GET

/api/v1/medias/{id}

Read media state, transcript, topics, and keywords

GET

/api/v1/clips

List clips across medias

POST

/api/v1/clips

Create a custom clip from a media

GET

/api/v1/direct_uploads

Obtain a signed upload URL and upload id

POST

/api/v1/webhook_subscriptions

GET

/api/v1/webhook_subscriptions

List webhook subscriptions on the account

POST

/api/v1/medias

Create a new media from a source URL or upload id

GET

/api/v1/medias

List medias in the account

GET

/api/v1/medias/{id}

Read media state, transcript, topics, and keywords

GET

/api/v1/clips

List clips across medias

POST

/api/v1/clips

Create a custom clip from a media

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

ContentGroove API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access at call time and never see the raw API key, so the same agent can call ContentGroove and other tools without leaking credentials across them.

Intent-based discovery

Agents search Jentic by intent (e.g. 'generate video clips with AI') and Jentic returns the matching ContentGroove media or clip operation along with its input schema, so the agent calls the right endpoint without crawling the ContentGroove docs.

Time to first call

Direct ContentGroove integration: 1-3 days for API key handling, direct-upload signing, webhook signature verification, and processing-state polling. Through Jentic: under an hour to search, load schema, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

AssemblyAI API

AssemblyAI provides speech-to-text and audio intelligence with deeper transcript-level features.

Choose AssemblyAI when accuracy of the transcript and speaker diarisation matter more than auto-clip suggestions.

Alternative

Deepgram API

Deepgram offers low-latency speech-to-text without ContentGroove's clip-suggestion layer.

Choose Deepgram for real-time transcription pipelines; choose ContentGroove when the goal is repurposing long-form video into shorter clips.

Complementary

Mux Video API

Mux handles video ingest, encoding, and streaming that complements ContentGroove's AI clip output.

Use Mux for delivering the source video and the generated clips at scale; use ContentGroove for the AI processing step.

Complementary

OpenAI API

OpenAI can summarise or rewrite the transcript ContentGroove returns into headlines or social copy.

Pair ContentGroove for clip and transcript generation with OpenAI for downstream summarisation, headlines, and translations.

FAQs

Specific to using ContentGroove API API through Jentic.

Why is there no official OpenAPI spec for ContentGroove API?

ContentGroove publishes a Swagger reference at developers.contentgroove.com but does not host a stable, agent-consumable OpenAPI 3 file. Jentic generates and maintains this spec so that AI agents and developers can call ContentGroove API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ContentGroove API use?

Server-side API keys are passed in the Authorization Bearer header, the X-API-KEY header, or the api_key query parameter. Through Jentic the API key is held in the MAXsystem vault and the agent never receives the raw key — only short-lived scoped credentials applied at call time.

Can I generate AI clip suggestions with the ContentGroove API?

Yes. POST /api/v1/medias creates a new media from either a source_url or a prior direct upload, and once processing finishes GET /api/v1/medias/{id} returns the transcript, topics, keywords, and AI-suggested clips. Custom clips can be added through POST /api/v1/clips.

What are the rate limits for the ContentGroove API?

ContentGroove returns 429 Too Many Requests when per-account rate limits are exceeded and 402 Payment Required when an account exceeds its plan quota; current usage is visible at app.contentgroove.com/quota_usage. Through Jentic, retries with exponential backoff are handled at the SDK level so agents do not need to implement throttling logic themselves.

How do I upload a large video with the ContentGroove API through Jentic?

Run `jentic.search('upload a contentgroove media')`, load the operation, and the workflow returned chains GET /api/v1/direct_uploads, a PUT to the signed URL, then POST /api/v1/medias with the upload id. File uploads are limited to 5 GB per file.

Does the ContentGroove API support webhooks?

Yes. POST /api/v1/webhook_subscriptions registers a callback URL that receives a JSON POST when a media finishes processing. The application must respond with HTTP 200; non-200 responses trigger retries with exponential backoff and webhooks must be treated as at-least-once.