Microsoft Text Translator

Microsoft Text Translator is a cloud-based translation service that provides accurate and reliable text translation capabilities across multiple languages, enabling businesses to break down language barriers and communicate effectively with global audiences.

Power end-to-end data operations for your Microsoft Text Translator API with Nexla. Our bi-directional Microsoft Text Translator connector is purpose-built for Microsoft Text Translator, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Microsoft Text Translator or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Microsoft Text Translator workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a Microsoft Text Translator credential, you need to obtain your API key (subscription key) from your Microsoft Azure account. Microsoft Text Translator uses API key authentication for all API requests, with the API key sent in the Ocp-Apim-Subscription-Key header.

To obtain your Microsoft Text Translator API key, follow these steps:

1. Sign in to the Microsoft Azure Portal using your Azure account credentials.

2. Navigate to All resources or search for Translator in the Azure portal search bar.

3. If you don't have a Translator resource yet, click Create a resource, search for Translator, and select Translator from the results. Then, click Create to set up a new Translator resource.

4. Configure your Translator resource settings:

   • Select your Subscription and Resource group
   • Choose a Region for your Translator resource
   • Enter a Name for your Translator resource
   • Select a Pricing tier (Free tier is available for testing)

5. Click Review + create, then Create to create your Translator resource.

6. Once your Translator resource is created, navigate to it in the Azure portal.

7. In your Translator resource, navigate to Keys and Endpoint in the left menu under Resource Management.

8. You will see two keys (Key 1 and Key 2). Either key can be used for authentication. Copy one of the keys (e.g., Key 1) and store it securely.

9. Store the API key securely, as you will need it to configure your Nexla credential. The API key is sensitive information and should be kept confidential.

The API key (subscription key) is sent in the Ocp-Apim-Subscription-Key header for all API requests to the Microsoft Text Translator API. The key authenticates your requests and grants access to the Translator service based on your Azure subscription and resource configuration. If your API key is compromised, you should immediately regenerate it in your Azure portal (Keys and Endpoint section) and update your credential. For detailed information about obtaining API keys, API authentication, and available endpoints, refer to the Microsoft Translator Text API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key Value	Yes	Yes	Your API key is your Azure secret key.

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Microsoft Text Translator

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

Microsoft Text Translator uses API key authentication for all API requests. The API key (subscription key) is sent in the Ocp-Apim-Subscription-Key header to authenticate API requests to the Microsoft Text Translator API.

3. Enter your Microsoft Text Translator API key in the API Key Value field. This is the subscription key you obtained from your Azure Translator resource (Keys and Endpoint section). The API key is sent in the Ocp-Apim-Subscription-Key header for all API requests to the Microsoft Text Translator API. The API key is sensitive information and must be kept confidential.

   Your Microsoft Text Translator API key (subscription key) can be found in your Azure Translator resource under the Keys and Endpoint section. The API key is sent in the Ocp-Apim-Subscription-Key header for all API requests to the Microsoft Text Translator API.

   If your API key is compromised, you should immediately regenerate it in your Azure portal (Keys and Endpoint section) and update your credential. The API key provides access to your Translator service and should be treated as sensitive information. Keep your API key secure and do not share it publicly.

   For detailed information about obtaining API keys, API authentication, and available endpoints, see the Microsoft Translator Text API documentation.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a destination

Click the + icon on the Nexset that will be sent to the Microsoft Text Translator destination, and select the Send to Destination option from the menu. Select the Microsoft Text Translator connector from the list of available destination connectors, then select the credential that will be used to connect to your Microsoft Azure Translator service, and click Next; or, create a new Microsoft Text Translator credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Microsoft Text Translator endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

Microsoft Text Translator - Make Translations

This endpoint template translates text from a source language to a target language using the Microsoft Text Translator API. Use this template when you need to automatically translate text content from your data flow into different languages for multilingual applications, content localization, or global communication.

• Enter the API version in the API Version field. This should be the version of the Microsoft Text Translator API you want to use (e.g., 3.0). The API version is included as a query parameter in the translation endpoint URL.
• Enter the source language code in the Source language (From) field. This should be the language code of the text you want to translate (e.g., en for English, es for Spanish, fr for French). Use language codes in ISO 639-1 format. You can also use auto to let the API detect the source language automatically.
• Enter the target language code in the Target language field. This should be the language code of the language you want to translate the text into (e.g., en for English, es for Spanish, fr for French). Use language codes in ISO 639-1 format. You can specify multiple target languages by separating them with commas (e.g., en,es,fr).

This endpoint sends text data as JSON in the request body to translate text from the source language to the target language. The request body should contain an array of text objects with a Text property containing the text to translate. The endpoint returns translated text in the same structure, with translations provided for each target language specified.

Language codes should be in ISO 639-1 format (e.g., en for English, es for Spanish, fr for French). You can use auto for the source language to enable automatic language detection. For detailed information about supported languages, language codes, API versions, and translation formats, see the Microsoft Translator Text API reference.

Manual configuration

Microsoft Text Translator destinations can also be manually configured to send data to any valid Microsoft Text Translator API endpoint, including endpoints not covered by the pre-built templates or custom request formatting. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Microsoft Text Translator API typically uses the POST method and expects JSON format. The endpoint URL should be the complete URL including the protocol (https://), the API base URL (api.cognitive.microsofttranslator.com), the endpoint path (/translate), and the required api-version, from, and to query parameters (e.g., https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=es). The request body should contain an array of text objects with a Text property (e.g., [{"Text": "{message.text}"}]), or you can use {message.json} to send the entire Nexset data as JSON. For detailed information about request body formats, supported languages, and translation options, see the Microsoft Translator Text API reference.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Microsoft Text Translator endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Microsoft Text Translator endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.