Upload

Getting Started (1.0.0)

Cincopa REST API V2 to get/set and manipulate assets and galleries

Cincopa REST API V2 is a simple set of REST based methods that allow you to access almost every aspect of your galleries and assets. Authentication is done with a simple api_token that can be created and deleted per app, set the permission level according to the needed level and exposure level.

V2 API was designed to be used:

  • in server-to-server scenario where the api_token and information is not exposed to the public, in such scenario the permissions level can allow write and delete.
  • in client-to-server scenario like javascript request from a public web page, in this scenario permission level will be set to read only which ensures the safety of your web app. This unique architecture eliminates the need of creating a "proxy" service that usually needed when working with a 3rd party API thus saving you time in integration.
Download OpenAPI description
index.json
index.yaml
Overview
Cincopa API Support support@cincopa.com
License MIT
Languages
Servers
Cincopa API
https://api.cincopa.com/v2/

General

This section offers foundational API endpoints essential for establishing and validating connections with the Cincopa platform. These endpoints are designed to ensure smooth integration and secure interactions between your application and Cincopa's services.

Key FunctionalitiesEndpointPurpose
Validate API Connection/ping.jsonThis endpoint allows you to confirm the validity and responsiveness of your API connection. By sending a request to /ping.json with your api_token, you can verify that your application is properly authenticated and can communicate effectively with Cincopa's servers.
Obtain a Temporary Token/token.get_temp.jsonIn scenarios where frontend applications require direct interaction with Cincopa's API, this endpoint provides a secure method to generate temporary tokens. These tokens facilitate client-to-server communications, enabling operations like updating galleries or assets directly from client-side code without exposing permanent credentials.
Operations

Gallery

This section provides a comprehensive suite of methods for managing your media galleries. The Gallery API empowers developers to programmatically create, manage, and customize multimedia galleries for seamless integration into applications, websites, or digital platforms.

Whether you're building a media-rich portal, a dynamic content hub, or a branded video experience, this API provides granular control over gallery configurations, media assets, permissions, and display logic.

Key FunctionalitiesEndpointPurpose
Creating Galleries/gallery.create.jsonEstablish new media galleries to organize your content effectively.
Setting Gallery Metadata/gallery.set_meta.json Update gallery information such as title, description, and custom properties to keep your content organized and accessible.
Deleting Galleries/gallery.delete.jsonRemove galleries that are no longer needed, ensuring your media library stays current.
Adding Items to Galleries/gallery.add_item.jsonIncorporate new media assets into existing galleries to enhance your content offerings.
Removing Items from Galleries/gallery.remove_item.jsonManage your galleries by removing outdated or unwanted media assets.
Listing Galleries/gallery.list.jsonRetrieve a list of all galleries in your account for easy management and overview.
Retrieving Gallery Items/gallery.get_items.jsonAccess detailed information about the media assets contained within a specific gallery.
Setting Master Media/gallery.set_master.jsonDesignate a primary media asset within a gallery to highlight featured content.
Operations

Assets

This section provides a comprehensive suite of methods for managing assets within your account. The Assets API enables developers to efficiently upload, organize, modify, and retrieve digital assets, ensuring seamless integration into applications, websites, or media platforms.

Whether you're handling large media libraries, automating asset management, or implementing structured metadata, this API offers precise control over asset creation, metadata customization, categorization, and retrieval, enhancing workflow efficiency and content organization.

Key FunctionalitiesEndpointPurpose
List Assets/asset.list.jsonGet a list of assets in the account; those assets can be added to any gallery. Use search to locate specific assets or use reference_id to locate by reference_id of the asset.
List Tags/asset.get_tags.json Fetches all tags associated with assets for categorization and filtering. Returns a structured list for efficient metadata management.
Set meta data of an asset/asset.set_meta.jsonUpdates or adds metadata (title, description, custom fields) for a specific asset. Requires the asset ID and enhances searchability and organization.
Resync an asset/asset.resync.jsonResync an asset will start a process of checking for missing versions and generating them. This method is only needed in cases of a failure to sync a gallery.
Delete an asset/asset.delete.jsonDelete an asset for good, it will be removed also from any gallery that exists.
Get upload URL to POST an asset./asset.get_upload_url.jsonGet upload URL to your assets library, use this URL with an HTTP POST method. Asset can be added directly to a gallery or be attached to another asset to set the video poster, for example. When attaching to another asset, it must provide a type name.
Start uploading an asset from an input URL./asset.upload_from_url.jsonUpload an asset from an input URL. Asset can be added directly to a gallery or be attached to another asset to set the video poster, for example. When attaching to another asset, must provide a type name. This method will return a status ID that can be used by asset.upload_from_url_get_status to get information about the upload process and the ID of the uploaded asset when done.
Get status during and after the uploading process./asset.upload_from_url_get_status.jsonUse this method to get the Id of the uploaded asset when done.
Abort uploading process./asset.upload_from_url_abort.jsonUse this method to abort an upload.
Operations

Upload

This section provides you with a detailed overview of Cincopa's Upload API, which allows users to upload media files to their Cincopa galleries efficiently. The API offers two primary methods for uploading content: an embeddable iFrame for direct user uploads and a secure token-based system for controlled access. These options ensure flexibility, security, and ease of use, making it simple to integrate media uploads into your applications or websites.

With the embeddable iFrame, users can upload media directly through an interactive interface that supports drag-and-drop functionality, media selection, and content management features like metadata editing and file reordering. On the other hand, the token-based system ensures that only authorized users can upload media by generating a secure upload token.

Key FunctionalitiesEndpointPurpose
HTML iframe to manage gallery/upload.iframeProvides an embeddable iFrame URL for users to upload media directly to a Cincopa gallery. The interface supports drag-and-drop uploads, media selection, metadata editing, reordering, and deletion. It is fully responsive across devices.
Invite upload token/upload.get_upload_token.jsonGenerates a unique token that restricts access to the invite upload page, ensuring that only authorized users can upload media to a specified gallery.
Operations

HTML iframe to manage gallery

Request

This method is actually a URL for an iframe which allows end users to upload media directly to a Cincopa gallery using an embedded iframe. This iframe provides a unified, simple interface to an end user for uploading using drag and drop, selecting media, editing the media information, reordering, and deleting. The iframe supports mobile, tablet, and desktop and will adopt the size and shape according to the site layout.

Here are some scenarios where this iframe can be used:

  • CMS system like WordPress and BuddyPress in an editor mode where the user can attach the media while in the authoring mode of a post, article or profile.
  • LMS system in teachers mode where the teachers can add media to a lesson
  • CRM system like Salesforce where media can be attached to any object, for example, a product object where the iframe can be added to the product's layout and allow adding videos, images, audio, and docs to that object.

Every media that is uploaded will reside in a gallery; this gallery can be referenced using two methods. Those two methods are interchangeable and were created to make the integration with the different systems much simpler:

  • Cincopa Identifier - this id (also known as FID) is issued by the API (or when creating a gallery in www.cincopa.com). When using FIDs your system should save it either in CMS page (like short code in WordPress) or in an extra field in the CRM object.
  • External Identifier - this id (also knows as RRID) is actually a remote reference given by your system, for example in WordPress this can be post id, in Salesforce this can be the unique id of the specific object.

Endpoint: GET /upload.iframe

URL: https://api.cincopa.com/v2/upload.iframe

Query
api_tokenstringrequired

A unique key used for authentication. Must be a valid API key provided by the system. Without the valid api_token, the request will be rejected with a 403 Unauthorized error.

Example: api_token=AAAAtAURG
fidstring

A unique identifier for a gallery. This parameter is used to specify the target gallery where the asset should be added.

Example: fid=A4KANh__rQ_m
rridstring

A remote resource ID that serves as a reference to a remote object, such as an entity in a CRM or CMS. This can be used as an alternative to fid when linking assets to external systems.

Example: rrid=5HN-847n_cyhene7
curl -i -X GET \
  'https://api.cincopa.com/v2/upload.iframe?api_token=AAAAtAURG&fid=A4KANh__rQ_m&rrid=5HN-847n_cyhene7'

Responses

When a request to this endpoint is successful, it returns an HTML response containing an embedded iframe link. The iframe can be used to display the uploaded content within a webpage or application.

Bodytext/html
string

The response consists of an HTML string containing an iframe. This iframe link allows direct embedding of the uploaded content into a webpage.

Response
text/html
<iframe width='100%' height='430' src='https://api.cincopa.com/v2/upload.iframe?api_token=cvdfjndv45' frameborder='0' allowfullscreen scrolling='yes' allow='geolocation *; microphone *; camera *'></iframe>

Invite upload token

Request

This API generates a special token that allows controlled access to an invite-based upload page. This token restricts access to the upload URL and ensures that only authorized users can upload files within a specified timeframe. The generated token must be included as a query parameter in the upload request to authenticate the upload session.

This API is useful for scenarios where temporary and restricted access to file uploads is required, such as inviting external users to contribute files without giving them full API access.

Endpoint: GET /upload.get_upload_token.json

URL: https://api.cincopa.com/v2/upload.get_upload_token.json

Query
api_tokenstringrequired

A unique key used for authentication. Must be a valid API key provided by the system. Without the valid api_token, the request will be rejected with a 403 Unauthorized error.

Example: api_token=AAAAtAURG
fidstringrequired

A unique identifier for the gallery where the uploaded assets will be stored. This helps link the uploaded content to the correct gallery.

Example: fid=A4KANh__rQ_m
expirestringrequired

The expiration date of the invite token in ISO 8601 format (YYYY-MM-DD). After this date, the token will no longer be valid, preventing further uploads.

Example: expire=2022-09-27
curl -i -X GET \
  'https://api.cincopa.com/v2/upload.get_upload_token.json?api_token=AAAAtAURG&expire=2022-09-27&fid=A4KANh__rQ_m'

Responses

When an upload token is successfully generated, the API returns a JSON response confirming the action. Below are the response parameters with corresponding descriptions and examples.

Bodyapplication/json
successboolean

Indicates whether the request was successful. true for success, false for failure. Always true for a 200 response.

Example: true
runtimeinteger

Specifies the total time taken to process the request, measured in milliseconds.

Example: 77
upload_tokenstring

A unique token that can be used to control access to the invite upload page. This token may be required for authentication or limiting the upload process.

Example: "LCJ1aWQiOiJBa0dBeWpoVlcwMGQiLCJleHBp"
Response
application/json
{
  "success": true,
  "runtime": 77,
  "upload_token": "LCJ1aWQiOiJBa0dBeWpoVlcwMGQiLCJleHBp"
}

Portal

This section provides a comprehensive suite of methods for managing and customizing portals. The Portal API allows developers to programmatically create, manage, and configure landing pages, video hubs, and share pages for seamless integration into applications, websites, or digital platforms.

Whether you're building a dynamic content hub, a multimedia-rich portal, or a branded video experience, this API offers full control over portal settings, status management, and retrieval of existing portals. The following table provides a breakdown of the available API endpoints and their functions:

Key FunctionalitiesEndpointPurpose
Verify subdomain/portal.check.jsonChecks if a portal exists and retrieves its status. This is useful for validating whether a portal is active before performing further operations.
Create subdomain if available/portal.cease.json Deactivates or ceases an existing portal. This operation is useful when a portal is no longer needed but should not be permanently deleted.
Rename subdomain/portal.rename.jsonRenames a specified portal by providing the existing portal ID and the new desired name. This helps in organizing portals efficiently.
Remove subdomain/portal.remove.jsonDeletes a portal from the system. This operation is irreversible and permanently removes all associated data.
Save subdomain/portal.set.jsonCreates a new portal or updates the settings of an existing one. This allows customization of portal properties such as name, visibility, and other configurations.
List of portals/portal.list.jsonRetrieves a list of all configured portals along with their details. This endpoint helps in managing multiple portals and tracking their statuses.
Operations

Webhook

This section provides a streamlined way to receive real-time notifications about account activities via HTTP POST callbacks. Instead of continuously polling for updates, webhooks allow external applications to listen for specific events and respond accordingly.

This API enables developers to automate workflows, synchronize data, and receive alerts whenever significant actions occur in the system. Additionally, the API supports Slack integration, allowing event notifications to be delivered directly to a Slack channel for easy monitoring and collaboration.

Key FunctionalitiesEndpointPurpose
List of webhooks/webhook.list.jsonRetrieves a list of all active webhooks associated with the account, including their configurations and callback URLs.
Create/update webhook/webhook.set.jsonRegisters a new webhook by specifying a callback URL and event types to trigger notifications.
Create/update webhook to slack/webhook.set_slack.jsonSets up a webhook that sends real-time event notifications directly to a Slack channel for instant updates.
Delete a webhook/webhhook.delete.jsonDeletes an existing webhook, stopping further event notifications and removing it from the system.
Operations

Live

Professional Live Video Streaming Service.

Operations