https://community.rws.com/developers-more/language-weaver/language-weaver-developers/en-USTelligent Community 12 Non-Productionhttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/60515/sdk-api-to-language-weaver-cloud/192103Thu, 19 Mar 2026 08:57:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:6d0f51f5-c8b4-4646-abe8-27c943380d36Adam LaMontagneHi Roger Shu , The LW SDK is the preferred method for developing integrations to Language Weaver simply because it makes the development easier. Fundamentally, the SDK is using the same API to communicate with Language Weaver. In any case, I'd like to point you towards the Language Weaver Developer documentation: https://developers.languageweaver.com/api/lw/index.html, where you will also find the SDKs for various languages as well as a Postman collection that can serve as a developer playground to help understand the API endpoints. All of the methods above support synchronous translation, asynchronous translation and https (recommended). Please share those details with the customer developers. We also recommend that LW integrations use https headers to identify themselves, making it easier to distinguish integration usage from other types of usage when reporting. The following headers should be sent with each HTTP request made to Language Weaver. Trace-App - [REQUIRED] Defines the Application Name for the integration - up to 128 chars Trace-App-Version - [REQUIRED] Defines the version of the integration. String - up to 128 chars Trace-App-Meta-Info - [OPTIONAL] Meta information that can be sent from the integration. String - up to 256 charshttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/60487/sdk-or-api-to-language-weaver-cloud/192059Wed, 18 Mar 2026 09:39:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:d33422d5-fbb5-4096-a2fd-82eb5f98df80Roger ShuDear Community fellows, Could anyone here help on this inforamtion pls? Appreciate for your time. Regards, Rogerhttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/w/language-weaver-wiki/7229/language-weaver-developer-quickstartThu, 05 Mar 2026 23:22:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:52126a83-e7d3-4d15-a8b7-167ffa9c3823Paul FilkinA practical guide for developers integrating with Language Weaver Cloud and Edge translation APIs. 1. Key Differences: Cloud vs Edge Aspect Language Weaver Cloud Language Weaver Edge Hosting RWS-hosted SaaS On-premise / self-hosted Base URL https://api.languageweaver.com/v4 https://{controller-host}:8001/api/v2 Authentication Client ID + Client Secret → Bearer token API key (HTTP Basic) or username/password → Bearer token Language codes 3-letter codes (e.g. eng , fra ) 3-letter codes (e.g. eng , fra ) Input encoding Base64 Base64 + URL-encoded Rate limits Account-tier dependent Limited by server capacity Both platforms share the same fundamental workflow: authenticate → discover language pairs → translate. 2. Authentication 2.1 Language Weaver Cloud Cloud uses an OAuth-style client credentials flow. You obtain a temporary bearer token using your client ID and client secret (found in the Language Weaver Cloud portal under Account Settings). Request: curl -X POST "https://api.languageweaver.com/v4/token" \ -H "Content-Type: application/json" \ -d '{ "clientId" : "YOUR_CLIENT_ID" , "clientSecret" : "YOUR_CLIENT_SECRET" } ' Response: { "accessToken" : "eyJhbGciOiJSUzI1NiIs..." , "tokenType" : "Bearer" , "validityInSeconds" : 86400 } Use the token in subsequent requests: curl -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIs..." \ "https://api.languageweaver.com/v4/languages" Tip: Tokens are valid for 24 hours. Cache and reuse them rather than requesting a new token per call. Refresh before expiry. 2.2 Language Weaver Edge Edge offers two authentication methods: Option A: API Key (HTTP Basic Auth) Admin users have a unique API key visible under [Username] > My Account in the Edge Web GUI. Pass it as the HTTP Basic username with an empty password: curl -u "YOUR_API_KEY:" \ "https://controller-host:8001/api/v2/language-pairs" Note: The trailing colon after the API key is required — it tells curl the password is blank. Option B: Username / Password → Bearer Token First, obtain a token: curl -X POST "https://controller-host:8001/api/v2/auth" \ -d username = "jsmith@example.com" \ -d password = "mypassword" This returns a JWT token valid for 30 days (configurable). Then use it: curl -H "Authorization: Bearer eyJhbGciOiJIUzI1NiIs..." \ "https://controller-host:8001/api/v2/language-pairs" Option C: SAML (Edge only) For SAML-enabled Edge instances, a three-step browser-assisted flow is available: GET /api/v2/auth/saml/gen-secret → returns a temporary SECRET Open GET /api/v2/auth/saml/init?secret=SECRET in a browser for user login GET /api/v2/auth/saml/wait?secret=SECRET → returns the access token once login completes 2.3 Authentication Errors Both platforms return 401 Unauthorized when credentials are invalid, expired, or missing. 3. Discovering Available Language Pairs Before translating, query the available language pairs to find the correct languagePairId . 3.1 Cloud curl -H "Authorization: Bearer YOUR_TOKEN" \ "https://api.languageweaver.com/v4/accounts/language-pairs" The response lists available language pairs with their identifiers, source/target languages, and capabilities. 3.2 Edge curl -u "YOUR_API_KEY:" \ "https://controller-host:8001/api/v2/language-pairs" Response (abbreviated): { "languagePairs" : [ { "languagePairId" : "EngFra_Generic_SRV_TNMV_8_4_x_1" , "sourceLanguage" : "English" , "sourceLanguageId" : "eng" , "targetLanguage" : "French" , "targetLanguageId" : "fra" , "domain" : "Generic" , "platform" : "SRV" , "technology" : "TNMV" , "version" : "8.4.1" , "linguisticOptions" : [ { "id" : "Formality" , "values" : [ "Informal" , "Formal" , "Polite" ], "systemDefault" : "Informal" } ] } ] } Useful Filters (Edge) Parameter Description sourceLanguageId Filter by source language, e.g. eng targetLanguageId Filter by target language, e.g. fra domain Filter by domain, e.g. Generic mode translation (default), installed , licensed , installedAndLicensed , adaptable chains also (default — includes chains), only , or excluded Example — find all English-to-French pairs: curl -u "YOUR_API_KEY:" \ "https://controller-host:8001/api/v2/language-pairs?sourceLanguageId=eng&targetLanguageId=fra" Language Pair Chains (Edge) Edge supports chained translation (e.g. Spanish → English → French) when a direct pair isn't available. Chains are identified by the >> separator in their languagePairId : SpaEng_Generic_SRV_TNMV_8_4_x_2>>EngFra_Generic_SRV_TNMV_8_4_x_1 4. Translating Text Both platforms require input text to be Base64-encoded . 4.1 Cloud — Synchronous Translation # Base64-encode your text echo -n "Hello, how are you?" | base64 # => SGVsbG8sIGhvdyBhcmUgeW91Pw== ​ curl -X POST "https://api.languageweaver.com/v4/mt/translations/async" \ -H "Authorization: Bearer YOUR_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "input" : [ "Hello, how are you?" ], "sourceLanguageId" : "eng" , "targetLanguageId" : "fra" , "model" : "generic" , "inputFormat" : "plain" } ' Note: Cloud also supports passing plain text strings directly in the input array for simple text translations, without Base64 encoding. Check the current Cloud API docs for the latest accepted formats. 4.2 Edge — Quick (Synchronous) Translation Best for small, plain text inputs under 1 KB: INPUT = $(echo -n "Hello, how are you?" | base64) ​ curl -X POST "https://controller-host:8001/api/v2/translations/quick" \ -u "YOUR_API_KEY:" \ -d languagePairId = "EngFra_Generic_SRV_TNMV_8_4_x_1" \ --data-urlencode input = " $INPUT " Response: { "languagePairId" : "EngFra_Generic_SRV_TNMV_8_4_x_1" , "translation" : "Qm9uam91ciwgY29tbWVudCBhbGxlei12b3VzID8=" } Decode the result: echo "Qm9uam91ciwgY29tbWVudCBhbGxlei12b3VzID8=" | base64 -d Auto Language Detection in Translation To automatically detect the source language, use AutXxx as the language pair ID, where Xxx is the 3-letter target language code: curl -X POST "https://controller-host:8001/api/v2/translations/quick" \ -u "YOUR_API_KEY:" \ -d languagePairId = "AutFra" \ --data-urlencode input = " $INPUT " Note: AutXxx cannot be used with language pair chains. 4.3 Edge — Asynchronous Translation For larger documents or when you need job tracking: Step 1 — Submit the job: curl -X POST "https://controller-host:8001/api/v2/translations" \ -u "YOUR_API_KEY:" \ -d languagePairId = "EngFra_Generic_SRV_TNMV_8_4_x_1" \ --data-urlencode input = " $INPUT " \ --data-urlencode inputFormat = "text/plain" \ --data-urlencode title = "My translation job" Response: { "translationId" : "bf91b9b6-d3c2-4ff2-ad3b-c9be89bd67fd" } Step 2 — Poll for status: curl -u "YOUR_API_KEY:" \ "https://controller-host:8001/api/v2/translations/bf91b9b6-d3c2-4ff2-ad3b-c9be89bd67fd" Check the state and substate fields. The job is complete when state is done and substate is succeeded . Job states: State Substate Meaning preparing created , scheduled , dispatching Job is queued inProgress translating , preprocessing , postprocessing Job is running done succeeded Complete — download results done failed Error — check errorMessage done canceled Cancelled by user Step 3 — Download the result: curl -u "YOUR_API_KEY:" \ "https://controller-host:8001/api/v2/translations/bf91b9b6-d3c2-4ff2-ad3b-c9be89bd67fd/download" Returns Base64-encoded output. Decode it to get your translated content. 4.4 Async Translation Options (Edge) The async endpoint supports many optional parameters: Parameter Description inputFormat MIME type of input (see §6 below) outputFormat MIME type of output; defaults to same as input encoding Character encoding; defaults to utf-8 dictionaryIds Comma-separated user dictionary IDs linguisticOptions E.g. Formality:Formal generateMetadata true to produce segment-level metadata labels Comma-separated labels for categorisation pdfConverter Standard or Abbyy for PDF inputs includeTextContent true to also produce a plain-text output 5. Language Detection 5.1 Cloud curl -X POST "https://api.languageweaver.com/v4/mt/translations/language-detection" \ -H "Authorization: Bearer YOUR_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "input" : "Bonjour, comment allez-vous ?" } ' 5.2 Edge Input must be Base64-encoded: INPUT = $(echo -n "Bonjour, comment allez-vous ?" | base64) ​ curl -X POST "https://controller-host:8001/api/v2/language-detections" \ -u "YOUR_API_KEY:" \ -d input = " $INPUT " \ --data-urlencode inputFormat = "text/plain" Response: { "encoding" : "UTF-8" , "languages" : [ { "code" : "fra" , "languageTag" : "fr" , "name" : "French" , "score" : 0.95 } ], "scripts" : [ { "code" : "Latn" , "name" : "Latin" , "percent" : 85.2 }, { "code" : "Zyyy" , "name" : "Common" , "percent" : 14.8 } ] } The response returns up to 3 detected languages with confidence scores (0–1), plus detected writing scripts with percentage breakdowns. 6. Supported Input/Output Formats (Edge) Input Formats Category MIME Type Extensions Plain text text/plain .txt HTML text/html .htm , .html , .xhtml XML text/xml .xml XLIFF 1.x application/x-xliff .xliff XLIFF 2.x application/xliff .xliff TMX text/x-tmx .tmx PDF application/pdf .pdf Word (OOXML) application/vnd.openxmlformats-officedocument.wordprocessingml.document .docx Excel (OOXML) application/vnd.openxmlformats-officedocument.spreadsheetml.sheet .xlsx PowerPoint (OOXML) application/vnd.openxmlformats-officedocument.presentationml.presentation .pptx Word (Legacy) application/msword .doc RTF application/rtf .rtf Images image/jpeg , image/png , image/tiff , image/gif .jpg , .png , .tif , .gif Email application/vnd.ms-outlook , message/rfc822 .msg , .eml OpenDocument application/vnd.oasis.opendocument.text (etc.) .odt , .ods , .odp Output Formats MIME Type Description default or empty Matches input format (with some exceptions for images/PDFs) text/plain Plain text application/x-xliff XLIFF v1.2 application/xliff XLIFF v2.1 text/x-tmx TMX 7. Language Codes Reference Both Cloud and Edge use 3-letter codes. Common examples: Language Code IETF Tag English eng en French fra fr German ger de Spanish spa es Chinese (Simplified) chi zh-Hans Chinese (Traditional) cht zh-Hant Japanese jpn ja Korean kor ko Arabic ara ar Portuguese por pt Portuguese (Brazil) ptb pt-BR Russian rus ru Dutch dut nl Italian ita it Polish pol pl Turkish tur tr Swedish swe sv Danish dan da Norwegian nor no Finnish fin fi Czech cze cs Hungarian hun hu Romanian rum ro Ukrainian ukr uk Hindi hin hi Thai tha th Vietnamese vie vi Indonesian ind id For the full list of 100+ languages, see the Edge language codes reference or query the Cloud API's languages endpoint. 8. Error Handling Both platforms use standard HTTP status codes: Code Meaning 200 Success 400 Bad request — invalid or missing parameters 401 Unauthorised — invalid, expired, or missing credentials 403 Forbidden — insufficient privileges 404 Not found — endpoint doesn't exist 500 Internal server error Error Response Format (Edge) { "error" : { "code" : 400 , "message" : "user could not be added" , "details" : "the specified user already exists: jsmith@example.com" } } The details field is optional and provides additional context when available. 9. Common Integration Patterns Pattern 1: Simple Text Translation Authenticate Base64-encode the source text Call the quick/synchronous translation endpoint Base64-decode the response Best for: chat integrations, real-time translation widgets, short text. Pattern 2: Document Translation with Job Tracking Authenticate Base64-encode the document Submit an async translation job ( POST /translations ) Poll status ( GET /translations/{id} ) until state=done Download the result ( GET /translations/{id}/download ) Best for: file-based workflows, batch processing, large documents. Pattern 3: Auto-Detect and Translate Authenticate Use the language detection endpoint to identify the source language Look up available language pairs for the detected source → desired target Translate using the appropriate language pair Alternatively, use AutXxx as the language pair ID to combine detection and translation in a single call (Edge only). Pattern 4: Batch Operations (Edge) Use the bulk download endpoint to retrieve multiple completed translations at once: curl -u "YOUR_API_KEY:" \ "https://controller-host:8001/api/v2/translations/download-archive?translationIds=ID1,ID2,ID3" Returns a zip file containing all requested translations. Total output size is limited to 1 GB. 10. Tips and Gotchas Always Base64-encode input text for Edge. Forgetting this is the most common integration mistake. URL-encode parameters when using form data with curl ( --data-urlencode ). Cache your auth tokens. Cloud tokens last 24 hours; Edge tokens last 30 days. Don't authenticate on every request. Check linguistic options. Some language pairs support formality settings (Formal, Informal, Polite). Query the language pairs endpoint to discover what's available. Edge timestamps use the format yyyy-MM-dd HH:mm:ss.SSS (e.g. 2024-01-02 15:04:05.999999999Z ). Character encoding defaults to UTF-8 on both platforms. Specify explicitly if your content uses a different encoding. Language pair chains (Edge) enable translation between language pairs that don't have a direct model, by routing through a pivot language (usually English). Quality estimation is available in async translation results on Edge, giving a breakdown of good/adequate/poor percentages. Further Reading Language Weaver Edge API Reference Language Weaver Cloud API Reference Language Codes (Full List) Supported Encodingshttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/w/language-weaver-wikiThu, 05 Mar 2026 23:01:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:c8371c36-c2b7-4891-ada6-33506154ba27https://community.rws.com/developers-more/language-weaver/language-weaver-developers/w/language-weaver-wikiThu, 05 Mar 2026 23:01:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:0fe6b936-519f-488b-b9b6-390fa60ea223Paul FilkinThis wiki provides essential information about the Language Weaver platform and how our integrations work with it. The goal is to empower your team with the technical and strategic knowledge needed to leverage our powerful translation technologies. You can expect to find information covering: Deployment options for Language Weaver, including Cloud and on-premise (Edge) solutions. The core Neural Machine Translation (NMT) technology, security features, and scalability. Our API-first approach and available connectors. Language pair types, including Generic, Adaptive, and Generative Language Pairs (GLPs). Customization options such as dictionaries, terminology controls, and OCR capabilities. Upcoming developments in Large Language Models (LLMs) and new platform features. Please explore the site navigation to find more detailed information on each of these topics.https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/60515/sdk-api-to-language-weaver-cloudThu, 05 Mar 2026 01:10:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:b47ca39e-9058-432d-97bb-70e026131845Roger ShuHi Dev team Our client’s plan is to establish the connection between their internal content platform with Language Weaver (Cloud) for synchronized translation, and would like to confirm some technical details. They are evaluating which method - SDK or API - would more proper for their platform and business demands. I searched but had very limited inforamation from Documentation and WIKI. Could you please help share your commments or suggest any? Appreciate for your help. Methods Support synchronized translation? Any links to detailed webpage? Support asynchronous translation? Any links to detailed webpage? Support HTTP? Any links to detailed webpage? Support HTTPS? Any links to detailed webpage? SDK method Yes？ ？ ？ ? API method Yes Synchronous translation - Wiki - Language Weaver - RWS Community ？ Yes Technical Requirements And Best Practices Yes Technical Requirements And Best Practices Best regards, Rogerhttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/60487/sdk-or-api-to-language-weaver-cloudTue, 03 Mar 2026 02:45:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:34de3b52-3c0a-4265-aa16-94012c610477Roger ShuHi Dev team Sorry for another question from the client The client’s plan is to establish the connection between their internal content platform with Language Weaver (Cloud) for synchronized translation. I searched but have very limited inforamation. Could you please help share your commments? Methods Support synchronized translation? And links? Support asynchronous translation? And links? Support HTTP? And links? Support HTTPS? And links? SDK method Yes？ ？ ？ ? API method Yes Synchronous translation - Wiki - Language Weaver - RWS Community ？ Yes Technical Requirements And Best Practices Yes Technical Requirements And Best Practices Best regards, Rogerhttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forumsThu, 12 Feb 2026 12:05:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2b9af082-2ed6-4417-b650-2982e540c80ehttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/Thu, 12 Feb 2026 11:51:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:607f62b2-3174-42f0-a0df-d2d71618c286https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/60094/language-weaver-sdk-in-java-and-spring-conflictTue, 13 Jan 2026 17:08:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:63433a0e-7f74-4ecf-8311-b94f9ccd7833Romain DénariéHi I'm trying to use Language Weaver Java SDK, last version (3.1.1, from march 2023) My application have dependencies on Spring, in a newer version from the one in the SDK, which generates conflict at startup. Is there a newer version of the SDK, with a more recent version of Spring, or without the dependency on Spring ? Thanks for your replyhttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/54737/blank-values-sending-data-to-the-api/174459Tue, 01 Oct 2024 16:14:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:01c6f5b4-1cb1-443b-8ec2-9786cf3ee707Chris WilliamsI use Postman regularly, however I've not configured it to use our proxy. That said, I've developed a Java SpringBoot application which communicates with the LanguageWeaver API, posting the following Translation Request attributes: private String sourceLanguageId ; private String targetLanguageId ; private String model ; private String submissionType ; private String inputFormat ; private String [] input ; private String [] dictionaries ; private String translationMode ; private String linguisticOptions ; private int qualityEstimation ; private String requestId ; In this context, the dictionaryID, copied from the " Do Not Translate" id. , is passed to this object which a post request sends this to the LanguageWeaver api. Since I do get a response with translated data, and the not translate variable I've configured using NO_1 TEXT_2 HERE_3, I'm confident the dictionaryId is being transmitted. I suppose I could try to configure Postman, but would rather work with my source code. Is this sufficient to diagnose this issue?https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/54737/blank-values-sending-data-to-the-apiMon, 30 Sep 2024 16:50:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:2ffcb411-4372-48c0-9dee-c50fed1ff301Chris WilliamsWhen I use the API to send an array of strings to translate, some of the values are blank (i.e. contain no value). This appears to throw a translation error. However using the Portal blank values are accepted. How can I translate an input with empty values (i.e., "one", "two", "", "three")https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/50488/api-accessMon, 18 Dec 2023 20:34:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:b8f424bc-8fce-4055-9516-a1060e1452a4Chris WilliamsHow do I determine what Language Weaver subscription level I have? I want to find out if I have access to the Language Weaver API for accessing your cloud services. According to the Language Weaver documentation: In order to get started developing on the cloud-based Language Weaver API, you need to create an account by visiting https://portal.languageweaver.com and signing up to plan that supports API integration. Once there, you can access your API credentials from the settings in your account. If you’re already a Language Weaver customer with a valid subscription, you can manage your API credentials from https://portal.languageweaver.com/settings/api-credentials . I'm a Language Weaver customer but how do I determine if I have a plan that supports API Integration.https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/47852/language-weaver-edge---using-it-locally-to-integrate-it-with-docker/153899Fri, 23 Jun 2023 07:32:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:5bb81c4f-ae6f-4534-b2e7-139ca8a8cd67Arnaud SimonHi Ben! Yes, Language Weaver Edge is designed to run locally, on-premise - and it supports multiple deployment types: You can deploy the application and the Language Pairs on Windows or Linux operating systems It can be deployed on bare metals servers, Virtual Machines or using containers. For Containers, you have 2 options: build your own docker image and run it using docker compose (we have building scripts available) or use our Kubernetes deployment package (with pre-defined images and customizable Helm Charts) For the integration part, you can use the RESTful API, which is documented at https://developers.languageweaver.com/api/lw-edge/index.html . We also provide additional options such as SDKs (Java, JavaScript, .NET) and embedded API (C++/.NET) Feel free to get in touch with our support or speak with one of our account managers to get access to the Language Weaver Edge software and start integrating it. And if you have any further question, feel free to use the forum. Thank you!https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/47852/language-weaver-edge---using-it-locally-to-integrate-it-with-dockerWed, 21 Jun 2023 18:45:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:195866a5-316a-4137-adba-7e7f84958cd3Ben HaHey guys! Hope you're doing well. Read this today in your docs: "Language Weaver Edge (formerly known as SDL Machine Translation Edge) 8 features a REST API that exposes the functionality of Edge to any HTTP client. It uses predictable, resource-oriented URLs as well as standard HTTP verbs and response codes. CORS is supported, allowing client-side web applications to make cross-domain AJAX requests to the API. The majority of the endpoints return JSON, while a few return a base64-encoded string or XML. The REST API is served on the controller host at its own port. To find out the API server host and port, log in to the Language Weaver Edge Web GUI as an admin user and click to [Username] > My Account . For the purposes of this documentation, we will reference an example server running at the host controller-host and port 8001 , with HTTPS enabled, so the base URL for the REST API will be: https://controller-host:8001/ Throughout the documentation, we will be using curl as our HTTP client to illustrate various interactions with the REST API. Keep in mind that, regardless of HTTP client, it is always a good idea to url-encode data that will be consumed by the API to ensure the integrity of the requests. " My question is simple - is it possible to use the Language Weaver Edge service locally? I mean, something like a `docker` container. I would like to know this because we're trying to integrate this service with a Golang processing application running on a docker container. Thanks in advance!https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/45715/using-language-weaver---automated-web-page-translation/148728Mon, 27 Feb 2023 09:19:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:42144a76-c2b4-44e1-9246-0f423c3b65beArnaud SimonHello Kevan, We are providing code samples together with the SDKs that Lenka mentioned in her reply ( https://developers.languageweaver.com/developer-tools/sdk/index.html ). Code samples are available from GitHub - for example the JavaScript code samples can be found at https://github.com/RWS/languageweaver-sdk-samples/tree/main/javascript You can find code samples for different implementations (backend or browser). In order to offer web page translation from your own web app, you will have to implement the UI part, but everything else, from language detection to html translation can be done with predefined operations available in the SDK. I hope this is helpful. The team is happy to get feedback on the SDK and hear from specific capabilities that our developers community would like to see implemented next. Thank you!https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/45715/using-language-weaver---automated-web-page-translation/148190Wed, 15 Feb 2023 22:14:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:a9717d95-bf48-40cf-b848-dee29ab6a689Lenka DenemarkHello Kevan, Are you trying to build an integration, or do you simply need to have a quick way to translate web sites? I assumed it was the former, but I also wanted to let you know that Language Weaver comes with browser plug-ins for Google Chrome, MS Edge, and Mozilla Firefox that provide on-the-fly machine translation of web pages. Can you please describe what you are trying to achieve? Best regards, Lenkahttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/45715/using-language-weaver---automated-web-page-translation/148110Tue, 14 Feb 2023 17:28:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:5dd9c6c7-d651-485a-9554-11d8fd5928e4Kevan StrangesIs there functions that have been prebuilt at all to help translate a page, as opposed to completely starting from scratch?https://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/45715/using-language-weaver---automated-web-page-translation/147942Fri, 10 Feb 2023 20:41:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:09b856a8-9643-4286-a7a3-8d56d0aca37dLenka DenemarkHello Kevan, It is possible to integrate Language Weaver to provide web site translation on the fly. If you are interested in building such integration, please refer to the Language Weaver Software Development Kit available at this link. https://developers.languageweaver.com/developer-tools/sdk/index.html I hope these resources will be helpful. Kindly let us know if you have any questions of if you need any further assistance. Best regards, Lenkahttps://community.rws.com/developers-more/language-weaver/language-weaver-developers/f/forums/45715/using-language-weaver---automated-web-page-translationThu, 09 Feb 2023 15:13:00 GMT10acfa76-f078-475b-a7ef-fc5b3e8d2934:1bcc6154-4041-4a2f-8f5f-a49d7bbde296Kevan StrangesHello, I was wondering if there was a way to integrate Language Weaver to translate web pages on the fly similar to the Google translate feature? Essentially something I can send as HTML, receive back and then just replace into the webpage, avoiding html classes like "no-translation" or something along those lines? If so, is there example JS to support this API? Thanks KevanHTMLautomatedhtml translationAPIJavaScript