This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 55.00000000000001%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPP%3C/text%3E%3C/svg%3E)
I am trying to create a custom translator using REST APIs. I looked at this Custom Translator documentation which doesn't mention details about creating custom translator using REST APIs. Does Microsoft support REST APIs to create custom translator?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 45%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGM%3C/text%3E%3C/svg%3E)
Hi, thanks for reaching out. Yes, REST APIs are available for custom translator. Please check out the following documentation. Hope this helps.
Currently we are using API Key credentials for authorisation purpose, however, that is not working while accessing these REST APIs. What is the authorisation method for accessing these REST APIs? Is there any documentation available for that?
Here's the API documentation (preview) for custom translator with sample code and authentication details. Consumption of the custom system is via the regular Translator API using the regular subscription key. The API call references the custom system via the &category= parameter.
I am able to access the Microsoft translator API using the Bearer access token however, while trying to access any of the custom translator REST APIs I am facing following error:
Also, I tried creating custom translator using the Azure custom translator Portal and was able to create it successfully, however, the REST APIs for the same are not working. Let me know how can I resolve this issue?
Thanks for following up. We are looking into this issue and will get back to you shortly.
Hi, following up. Based on feedback received from the product team, you will have to interactively authenticate and the auth token has a limited lifetime in which it can be used. More information is provided in this document.