Summary

Unique does publish some events at certain points of the ingestion progress. Customers having access to the SDK can subscribe to those events and react asynchronously with custom implementations. E.g. doing the whole ingestion by themself or adding custom metadata opf content that has finished the ingestion.

Events

Customers with access to the SDK can register their application in Unique App Repository. During this process they can select to which events the application should subscribe. There are the following two events specifically related to the Unique Ingestion.

Uploaded

The event named unique.ingestion.content.uploaded will notify the applications subscribe to this event about every content that has been uploaded completely. Means currently a normal content upload contains of the following three steps:

initialise the content object and getting the URL to upload the file
uploading the file
notify Unique that the file got uploaded (fileUrl)

On Step three this event gets published. The event has the following payload:

{
  "contentId": "<idOfContent>",
  "mimeType": "<mimeType>",
  "ingestionConfig": {<ingestionConfigOfTheContent>}
}

Finished

As soon as a content gets marked as finished Unique is publishing an event called unique.ingestion.content.finished. This event has the following payload:

{
  "contentId": "<idOfContent>"
}

Author	@Adrian Gugger

Public Documentation

Ingestion Events

Summary

Events

Uploaded

Finished