Spike for end-2-end flow of cielo24

We will test Cielo24's callback functionality via sandbox account and for testing the original turnaround time & statuse, we will get a live account – confusions are no more, closing this!

What we need to close this task ?

According to cielo24's API documentation , we will:

1. Create a job: http://docs.cielo24.com/en/latest/job_control/create_job.html

2. Add Media (video) to job: http://docs.cielo24.com/en/latest/job_control/add_media_to_job.html – A job can only have one associated media and this can be added via video binary file or via link in media_url query parameter.

3. Perform transcription: http://docs.cielo24.com/en/latest/job_control/perform_transcription.html – Provide callback urls to track transcription process.

4. Get transcript/captions: http://docs.cielo24.com/en/latest/job_control/get_transcript.html OR http://docs.cielo24.com/en/latest/job_control/get_caption.html

I've made collection on this workflow which can be found on Postman. The job and transcription process is getting completed successfully on sandbox but when I'm not getting right file when I try to get transcript – i.e. step4.

I'm also getting incorrect job's media info on sandbox, response:

That's malformed and somewhat combination of production api base url i.e. http://api.cielo24.com and sandbox api base url http://sandbox.cielo24.com. I'm unsure if sandbox account actually stores and uses the media file for transcription on cielo24.

FYI , .