Hello Vandanaa !
Thank you for posting on Microsoft Learn Q&A.
The glossary URL you’re passing is being ignored because the translate API doesn’t accept a glossaries file in the request body.
TSV glossaries are only supported by the document translation API and for real time text calls you have 2 options:
- use the dynamic dictionary markup inline
- deploy a Custom Translator model and pass its category id
If you need real time chat translation (you can keep using POST and remove the customization.glossaries block and it’s not a supported field for this endpoint.
You can use dynamic dictionary markup for the terms you must preserve, and you must specify from= or, if the terms list is large and stable, you can train a custom translator model and pass &category=<your-custom-model-id> on the query string.