Immersive Translate custom API setup

Open the OpenAI service settings

Immersive Translate's official OpenAI service page documents a custom API address under More Settings. Start there when evaluating an OpenAI-compatible endpoint. Record the extension version and browser so a later setup check refers to a reproducible environment.

Choose one configuration for the first test and keep the default settings available for recovery. Enter the credential only in the private extension settings. Confirm that the endpoint is the intended recipient before sending any page content, especially when the browser also has access to merchant administration screens.

Check whether the address is a base or a full route

Do not assume every custom-address field behaves like an SDK baseURL. The official page includes a full chat-completions URL in its Azure example. Inspect the help text in your installed extension and the sanitized outgoing request path to determine how the address is used.

For an APIsRouter chat-completions candidate, the full route is https://api.apisrouter.com/v1/chat/completions. If your installed version explicitly expects a base URL and appends the route, use https://api.apisrouter.com/v1 instead. Avoid a duplicated chat/completions suffix. The worksheet below describes candidate settings, not a tested extension configuration.

Service: OpenAI
Settings area: More Settings > custom API address
Full request URL candidate: https://api.apisrouter.com/v1/chat/completions
Base-only candidate, if required by installed version: https://api.apisrouter.com/v1
Credential: gateway key entered privately
Model: exact current catalog ID with verified chat behavior

Keep the translation request path visible

The extension sends translation requests to the selected service address. Treat that address as a data-sharing decision, not only a connectivity field. Use content you own or may process through the chosen endpoint, and review how much of a page the selected translation action includes.

The flow below illustrates the proposed gateway path using the documented custom-address mechanism. The selected-model label is a configuration choice, not a list of verified models. Store authentication, product editing and import approvals are outside this request path.

Verify one controlled page first

Use a short page with a synthetic product description, a protected brand term, a quantity with its unit and a link. Translate only that page. Compare the visible result with the source and inspect the sanitized network destination, selected model and response status.

Check whether content is omitted, duplicated or mixed with the source language. Then try a longer paragraph and a layout with headings or lists. Save the source and observed output so a later configuration change can be compared against the same material. This gives you a useful diagnostic baseline before processing a large document.

Use bilingual reading for editorial questions

Browser translation can help a reviewer inspect unfamiliar source material or identify a phrase that needs attention. Keep the original visible and compare claims, quantities and terminology directly. If the reviewer cannot evaluate the target language, route the candidate to someone who can rather than accepting fluent appearance as proof.

Keep glossary decisions in the catalog workflow. Do not assume a custom endpoint also supplies glossary enforcement or field-level validation inside the extension. Product descriptions intended for import still need their own source-linked candidate, review result and destination mapping.

Diagnose errors before translating more content

Begin with the request path, credential and exact model ID. Record structured errors where available and redact headers before sharing evidence. If requests are limited, reduce the workload and respect the service's retry guidance rather than rapidly repeating a full-page translation.

Use a smaller selected passage to distinguish connection failure from content or response-handling problems. Change one setting at a time. The official page contains historical price and request-rate examples; use your current endpoint's documentation and account limits instead of copying those numbers into a new setup.

Separate browser output from catalog delivery

A translated browser view is an inspection surface. To publish product text, create a candidate in the catalog review package, preserve identifiers and source revisions, then pass approved fields through the store's actual import or translation API.

Verify delivery by reading stored fields and opening the intended storefront locale. Do not rely on an editor's browser extension to prove what an ordinary visitor will see. Record translation request usage separately from store operations, and account for retries when evaluating the workload. Refer to current pricing instead of assuming a fixed cost per page or character.

Evidence and integration limits

The official documentation establishes a custom-address setting. An installed-extension request through APIsRouter has not been tested for this article, so the precise address behavior, model compatibility and rendered result remain setup checks. The diagram is an illustrative configuration flow.

A completed compatibility record should include extension and browser versions, sanitized settings, request destination, exact model, a controlled source page and observed translation. Keep protected-field review separate from that transport check. A successful short passage does not automatically validate every document format or a store publishing workflow.

FAQ