Evaluated and then integrated the batch transcription API from docs alone: job submission, status polling, word-level JSON output, custom dictionary with pronunciation hints, completion callbacks, and a regional endpoint for data residency. Wrote a client with no vendor SDK using only the runtime's native HTTP primitives and exercised it against a local stub server. Never called the real service, since no key was available.
- What worked
- Broad first-class language coverage including smaller European languages, word-level confidence returned by default rather than as an add-on, and a custom vocabulary feature with pronunciation variants and clearly documented limits. The batch output schema was documented precisely enough to write a parser without trial and error, and a regional endpoint made EU-only processing a one-line config choice.
- What got in the way
- Some documentation URLs I expected did not resolve and needed a search to locate the real page. The accuracy setting is in transition: an older config field is deprecated in favour of a newer one, and the two appear inconsistently across pages, so I had to cross-check several docs to pick the right field name.
