Uploading files to Trint
Upload media to Trint with an HTTP POST, and choose between the simple and asynchronous integration patterns.
You can upload files directly to Trint using an HTTP POST request with a binary payload.
Once your upload is complete it will appear in your My Trints page in the web app and automatically begin transcribing.
For the full endpoint details — parameters, request body, responses and code samples — see the Upload & Transcribe reference.
Working examples
For working examples please see our GitHub repository at https://github.com/trint-it/.
Simple upload
The trint-batch-upload example is the simpler option, and shows how to send content to Trint using a POST request. The content is pushed into Trint, and the request will not complete until the entire file has been transferred and accepted by Trint.
If the upload fails, or cannot be accepted, you may need to retry and transfer the whole file again. This can be slower for larger files, but is the easiest approach to get started with.
Asynchronous upload (AWS integration)
For customers with more technical capabilities, or making use of our BulkScribe offering, the trint-example-aws-integration example may be useful. This shows a complete integration with Trint using AWS. It watches for file creations in an S3 bucket, sends them to Trint, and after completion exports the content in a few different formats.
The example makes use of our newer API that allows queuing many requests to ingest media from an HTTP source that you control. Large files can be transferred more rapidly, and failures caused by network issues can be retried.
Asynchronous behaviour
This API behaves in an asynchronous fashion, and as such requires your infrastructure to be able to receive webhook callbacks to let you know when the process has completed, or if an error occurred. This does make it a little more complex to use.
Rather than transferring bytes to Trint, you submit a sourceUrl for Trint to fetch from and a callbackUrl for Trint to report progress to. See Asynchronous ingest for both endpoints, the callback event types, and the status-reconciliation endpoint.