Get Transcript By Id in REV Asynchronous Speech To Text Documentation
A documented REV Asynchronous Speech To Text Documentation operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get Transcript By Id
- GETReads data · Transcript
api.rev.ai/jobs/{id}/transcript
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which REV Asynchronous Speech To Text Documentation operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other REV Asynchronous Speech To Text Documentation operations
- Submit Transcription JobPOST · changes data
- Delete Job by IdDELETE · changes data
- Get List of JobsGET · reads data
- Get Job By IdGET · reads data
- Get CaptionsGET · reads data
All 7 REV Asynchronous Speech To Text Documentation operations
Questions
- Can HumDay get transcript by id in REV Asynchronous Speech To Text Documentation?
- Yes. This operation is published in REV Asynchronous Speech To Text Documentation's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my REV Asynchronous Speech To Text Documentation account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in REV Asynchronous Speech To Text Documentation.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your REV Asynchronous Speech To Text Documentation account.
Where this came from
Read from a published API description for REV Asynchronous Speech To Text Documentation at api.rev.ai/openapi/v1/documentation.yaml. The description above is the provider’s own wording, not ours. Last published 2021-08-02.