Feature Request: Support custom base URL for OTA Client (proxy support)

[frederikreher]

We’d like to request support for configuring a custom base URL in the OTA Client instead of always using Crowdin’s default distribution endpoint.

Motivation

In some setups (e.g. GDPR-sensitive or enterprise environments), applications need to route OTA traffic through their own backend:

Browser → App backend → Crowdin

instead of:

Browser → Crowdin

Currently, the client makes direct requests to Crowdin, which exposes end-user IP addresses and prevents proxy-based setups.

Proposal

Add an optional configuration field, for example:

new OTACrowdinClient({
  distributionHash: "...",
  baseUrl: "https://api.myapp.com/crowdin-proxy"
});

If baseUrl is provided, the client would use it instead of the default Crowdin endpoint. If not, behavior remains unchanged (fully backward compatible).

Would you be open to accepting a PR adding this functionality?
Happy to contribute an implementation.

Thanks!

[andrii-bodnar]

Thanks for the suggestion!
Supporting a custom proxy is feasible, provided the proxy mirrors the Crowdin Distribution structure (specifically the manifest and file paths). Since the OTA client relies on this specific architecture to handle CDN content delivery efficiently, any proxy would need to maintain that interface to function correctly.