Curator includes a large number of integrations and device connectors to drive workflows. Additionally, Curator’s core workflows provide powerful automation capabilities and configurable functionality.

Curator’s workflows can be started from Curator applications, including Clip Link, Clip Select, Curator Logger, and Curator for Adobe. However, there are also occasions where you may want to start a workflow from your own automated process. Curator’s API Functionality Module gives you access to REST and SOAP APIs allowing you to start workflows, monitor status, and consume results.

Curator’s API Functionality Module includes access to the API, HTML API reference, REST API sample in a Postman collection, SOAP API sample coded in C# and technical reference diagrams.

Additional, tailored samples can be provided via Professional Services showing you how to complete specific tasks or call APIs in your environment.

Example uses  

Curator’s API Functionality Module can be used to:  

• Create a new asset from a media file
• Create a placeholder asset for media which will be received later
• Create a production task for video editors
• Search and find assets, including metadata
• Add, update and delete asset metadata
• Get asset thumbnails for presentation on an external user interface
• Get metadata fields and types, including configured metadata views
• Get a list of client applications available in the Curator system, including the URL for each Curator user interface
• Get a list of users and groups (controlled via permissions and only available to authorized API users)

What’s included?

Curator’s API Functionality Module includes the following:

• Access to Curator’s API through Curator’s Gateway service
• API reference documentation in Postman format. Curator’s API and documentation includes version information
• Configuration of your service as an API client within the Curator Gateway