Clipnow API


For clarity the resources are abbreviated, just using the variable part of the HTTP REST request. The base-URLs are or (first for HTTP, second for HTTPS).

For example, a resource described like /clip is an abbreviation of the real resource: http(s)://

Clipnow REST API supports HTTP and HTTPS for all its resources. It's up to the customer to select one or the other, but we encourage to choose HTTPS due to evident security considerations.

Resource NameResource DescriptionResource URL without ${base-URL}Resource HTTP method
Create clipCreate a new clip./clipPOST (multipart/form-data)
Search ClipRetrieve the list of clips belonging to the logged in user/clipGET
Search ClipRetrieve the information related to a concrete clip/clip/{uuid}GET
Search clipsRetrieve the list of clips belonging to the logged in user with a set of filtering parameters/clip/{uuid}/searchPOST
Status ClipGet information related to the clip process/clip/{uuid}/statusGET
Upload to YouTubeUpload an already created clip to YouTube/clip/{uuid}/youtubePUT
Delete from YouTubeDelete a previous uploaded clip from YouTube/clip/{uuid}/youtube



  • The chapter Handling errors specifies the errors that can occur in Clipnow API response.

  • The chapter Result response defines an optional process where the customer can receive a message once the clip creation process has finished.

  • The chapter Entities/enums defines all the Entities or Models used in the exchange with the API.

  • The  Java code attached contains the entities defined and the REST connection with the Clipnow API. Once you have the proper credentials, use the test classes (ClipConnectorTest and YoutubeConnectorTest) to test the process.

  • The XSD scheme attached contains the entities definitions in XSD format for exporting it to other programming languages.

Check changelog for latest changes.


Contact us for API credentials request, result integration or any other issue related with the API: