Post Process MQ Interface
filespin-asset-post-process application reads messages from filespin-asset-post-process queue and invokes addons that process assets.
The messages are sent to the queue by filespin-saas-backend application.
Message format
{
"apikey": "API_KEY" ,
"asset_id": "ASSET_ID",
"event_type": "file-data-updated",
"addons": ["SCENE_CLASSIFICATION", "EMOTION_RECOGNITION"],
"force_processing": false,
"asset_data": null
}
apikeyis used to make API calls to get user's addon settings and to invoke addon API.asset_id- is the id of the asset that needs to be processed.event_type- specifies the event type for which the addons are invoked (seeAsset Events)addons- specifies the list of addons that need to be invokedforce_processing- optional, defaults to falseasset_datacontains the asset data in Asset Data Format only when the event isfile-deleted- This is to allow post-process to handle assets that have been deleted and purged already when post-process picks up the message for processing the asset