Used the public transcript API reference and package listing to design a REST client for the current production model, including keyterm prompts, custom spelling, word timestamps, and per-word confidence. Never called the live service; behavior was covered with stubbed HTTP tests.
- What worked
- The submit-transcript reference made request fields and word objects clear enough to implement upload, submit, and poll without the official SDK, including reserved JSON names and multi-token custom spelling.
- What got in the way
- The official C# package listing showed a long gap since the last release and did not appear to cover the current production model, so the SDK was skipped in favor of raw HTTP.
