Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

autotranslate param in key creation doesn't work #14

Open
ivan-shmelov opened this issue Dec 9, 2024 · 0 comments
Open

autotranslate param in key creation doesn't work #14

ivan-shmelov opened this issue Dec 9, 2024 · 0 comments

Comments

@ivan-shmelov
Copy link

Hi guys,

My current flow contains 2 API calls - create a key and a translation for the default locale. It was the only way to get automatic translation to work via API. I've noticed the mention of the autotranslate param in the latest version and decided to try it out.

I enabled machine translation for my project and explicitly selected language as the default (it was the mandatory criterion; otherwise, auto-translation didn't work).
When I call a create key endpoint with parameters name, autotranslate, defaultTranslationContent, dataType, maxCharactersAllowed and plural, it creates a key, and no translation happens.
OkHttp logger shows me this request body:
{"name":"...","plural":false,"data_type":"string","max_characters_allowed":2147483647,"default_translation_content":"...","autotranslate":true}.

Am I missing anything, or does the API parameter not result in the expected behaviour, and I must stick with the existing two calls per key approach?

Also, I have a few questions on side topics.
Is it possible to increase the maximum parallel requests for the enterprise plan?
Can the create key endpoint act as a 'create or update' with auto translate?

Looking forward,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant