In production mode you should never use localization data from Tolgee REST API and you should never leak your API key. You should use data exported from Tolgee platform. To get exported localization files, see exporting translations.
There are multiple options to provide static localization data for production builds. Providing a URL prefix where Tolgee can
fetch the data from or providing imported data as reference or provider in
NgxTolgeeModule.forRoot(...) config property.
To provide your localization data using dynamic import you will need to add providers for every supported language to staticData configuration property.
Using this approach data will be fetched just when it's needed, so you will save some network traffic.
This approach just provides localization data as imported object.
This way, all localization data are bundled with your application, so it will be downloaded with your application code.
This option tells Tolgee, that localization data (en.json, cs.json) can be found on
so it will be fetched with every page load.