I’m a dev at a video production company. We want to programmatically understand when editors have uploaded new drafts into certain folders in box, but when they use applications like Adobe Media Encoder/Adobe Premiere to render video directly to a folder in Box Drive, Box Drive uploads the file incrementally as it's being written, as it doesn’t understand when the file is fully rendered and ready to be properly uploaded.
This triggers multiple FILE.UPLOADED webhooks throughout the render process.
For example, when rendering 592.4 MB file, I received 3 FILE.UPLOADED payloads at
- 0.09 MB
- 184.77 MB
- 592.4 MB (render actually complete + fully uploaded)
Am I correct that the best workaround for this issue (for assets that generate thumbnails according to https://developer.box.com/guides/representations/thumbnail#supported-file-types) is to:
Use the Representations API to check if Box can generate a thumbnail. From my testing, only complete, valid video files produce thumbnails.
GET /files/{file_id}?fields=representations
x-rep-hints: [jpg?dimensions=32x32]
When representations.entries[0].status.state includes:
- error → file is incomplete/invalid
- success or viewable → file is complete, safe to process
Is this the best way of doing so? It’s not totaIly ideal because we will burn one of our limited API calls every time we GET representations on a still-rendering video, but I’m not sure of a better way to do this, aside from making the uploaders render locally, or to a not-watched folder first.
Thanks!
Paul