Cincopa REST API V2

Name: Cincopa REST API V2 API
Brand: Cincopa REST API V2
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey19 EndpointsREST

For Agents

Upload, tag, and organise media assets in Cincopa galleries, and manage gallery membership and metadata for embed-ready video and image experiences.

Quickstart

Get started with Cincopa REST API V2 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:
"upload a video to a gallery"

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

Capabilities

What an agent can do with Cincopa REST API V2 API.

Upload images, video, and audio to Cincopa via /asset.upload_from_url.json or signed upload URLs from /asset.get_upload_url.json

Resync remote assets to refresh transcoded variants via /asset.resync.json

Tag and retag assets and read tag taxonomies via /asset.set_meta.json and /asset.get_tags.json

Compose galleries by adding and removing assets via /gallery.add_item.json and /gallery.remove_item.json

GET STARTED

Start building with Cincopa REST API V2 API

Explore with Jentic

View OpenAPI Document

Use for: Upload a hero video to a Cincopa gallery from a public URL, Find all Cincopa assets tagged with a specific campaign label, Add an existing asset to a marketing gallery and set it as the master, Issue a temporary token so a browser client can read a gallery without exposing the master api_token

Not supported: Does not handle live streaming, DRM packaging, or video editing — use for media hosting and gallery composition only.

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

Jentic publishes the only available OpenAPI specification for Cincopa REST API V2, keeping it validated and agent-ready. Cincopa is a media hosting and gallery platform that lets developers manage image, video, and audio assets along with the galleries that present them. The REST API V2 exposes 19 endpoints for asset upload, tagging, gallery composition, and metadata management, with separate read/write modes for server-to-server flows and read-only client tokens. Authentication uses an api_token passed as a query parameter.

Use Cases

Patterns agents use Cincopa REST API V2 API for, with concrete tasks.

★ Server-Side Media Upload Pipeline

Push images and video into Cincopa from a backend job by requesting an upload URL or supplying a remote URL, then tagging the new asset and adding it to the right gallery in a single workflow. The /asset.get_upload_url.json and /asset.upload_from_url.json endpoints support both direct binary upload and remote ingestion, while /asset.set_meta.json applies tags and metadata as the asset is created.

Call /asset.upload_from_url.json with the source URL and gallery ID, then call /asset.set_meta.json to attach campaign tags and a description.

Gallery Composition for Marketing Pages

Build and rearrange Cincopa galleries that drive product, blog, and landing page experiences by adding or removing items, designating a master asset for hero positioning, and updating gallery metadata. The /gallery.add_item.json, /gallery.remove_item.json, /gallery.set_master.json, and /gallery.set_meta.json endpoints together cover the curation workflow without writing custom CMS code.

Add asset abc123 to gallery xyz789 via /gallery.add_item.json then mark it as the gallery master via /gallery.set_master.json.

Browser-Safe Read-Only Embeds

Embed Cincopa galleries on public sites without leaking the master api_token by minting a short-lived read-only token via /token.get_temp.json and passing it to the browser. This keeps the privileged token on the server while the client can still load gallery metadata and assets for rendering.

Mint a temporary read token via /token.get_temp.json scoped to a single gallery and return it to the browser embed code.

AI Agent Media Curation via Jentic

An AI agent receives a request to add a new product video to a marketing gallery, searches Jentic for the upload-and-attach operations, and calls Cincopa via Jentic without ever holding the api_token. Jentic vaults the credential and the agent only sees the schema for the relevant /asset and /gallery operations.

Use the Jentic search query 'upload a video to a gallery' to find the Cincopa upload and add-item operations and execute them with the new product video URL.

Key Endpoints

19 endpoints — jentic publishes the only available openapi specification for cincopa rest api v2, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/asset.get_upload_url.json

Request a signed upload URL for direct binary upload

POST

/asset.upload_from_url.json

Ingest a remote asset by URL

POST

/asset.set_meta.json

Set metadata and tags on an asset

POST

/gallery.create.json

Create a new gallery

POST

/gallery.add_item.json

Add an asset to a gallery

POST

/gallery.set_master.json

Designate the master asset for a gallery

POST

/token.get_temp.json

Mint a temporary read-only API token

POST

/asset.get_upload_url.json

Request a signed upload URL for direct binary upload

POST

/asset.upload_from_url.json

Ingest a remote asset by URL

POST

/asset.set_meta.json

Set metadata and tags on an asset

POST

/gallery.create.json

Create a new gallery

POST

/gallery.add_item.json

Add an asset to a gallery

Why though Jentic?

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

Credential isolation

The Cincopa api_token is stored encrypted in the Jentic vault. Agents receive scoped execution rights and never see the raw query-parameter token.

Intent-based discovery

Agents search Jentic by intent such as 'upload a video to a gallery' and Jentic returns the matching Cincopa asset and gallery operations with their input schemas.

Time to first call

Direct Cincopa integration: 0.5-1 day to wire up upload, tagging, and gallery composition. Through Jentic: under 30 minutes.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloudinary Upload API

Image and video upload, transformation, and delivery API

Choose Cloudinary when you need on-the-fly image and video transformations alongside hosting rather than gallery composition.

Alternative

Vimeo

Video hosting platform with player, privacy controls, and analytics

Choose Vimeo when the use case is single-video player embeds with creator-grade privacy and analytics rather than multi-asset galleries.

Complementary

Mux

Video streaming, encoding, and analytics API

Pair Mux when you need adaptive bitrate streaming and per-view analytics on top of asset hosting.

FAQs

Specific to using Cincopa REST API V2 API through Jentic.

Why is there no official OpenAPI spec for Cincopa REST API V2?

Cincopa does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cincopa REST API V2 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 Cincopa REST API V2 use?

The API uses an apiKey called api_token passed as a query parameter on every request. Through Jentic the api_token is stored in the encrypted vault and the agent never receives the raw value, only a scoped execution context.

Can I upload a video to Cincopa from a remote URL?

Yes. Call /asset.upload_from_url.json with the source URL and the target gallery, and Cincopa will fetch and transcode the asset. Upload status can be polled via /asset.upload_from_url_get_status.json.

How do I add an asset to a Cincopa gallery through Jentic?

Search Jentic for 'add a video to a gallery', load the schema for /gallery.add_item.json, and execute with the gallery and asset IDs. The Python SDK uses await client.search, await client.load, await client.execute.

How do I generate a browser-safe read-only token?

Call /token.get_temp.json on the server with the master api_token to mint a temporary read-only token, then pass that scoped token to the browser embed. The master token never leaves the server.

How do I tag a Cincopa asset and read tags back?

Use /asset.set_meta.json to attach tags as metadata and /asset.get_tags.json to read the tag taxonomy for an asset. Tags drive search and gallery filtering downstream.