You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Add support for styleGuideIds in AI Translation methods #387
The Crowdin API exposes an optional styleGuideIds field on the AI Translation request bodies in both Crowdin and Crowdin Enterprise. It is an array of Style Guide identifiers used as context during AI translation. API client libraries should expose styleGuideIds on these requests so consumers can pass style guides via the SDK.
Affected endpoints:
AI Translate Strings — api.users.ai.translate.strings.post (Enterprise: api.ai.translate.strings.post)
AI File Translation — api.users.ai.file-translations.post (Enterprise: api.ai.file-translations.post)
Hi! I would like to work on this. I plan to add optional styleGuideIds support to both AI strings translation and AI file translation request models, cover Crowdin and Enterprise call paths through the shared models, and add focused serialization/model tests. I will keep the change backward-compatible and run the project test suite before opening the PR.
Update after checking the latest master: this appears to have just landed in #379 (feat: add styleGuideIds to AI Translation requests). Both request models and API mock fixtures/tests already cover the field, so I will not open a duplicate PR. Maintainers can likely close this issue as completed by #379. I am stepping back from it.
Activity
77cjj commentedon Sep 5, 2026
Hi! I would like to work on this. I plan to add optional
styleGuideIdssupport to both AI strings translation and AI file translation request models, cover Crowdin and Enterprise call paths through the shared models, and add focused serialization/model tests. I will keep the change backward-compatible and run the project test suite before opening the PR.77cjj commentedon Sep 5, 2026
Update after checking the latest
master: this appears to have just landed in #379 (feat: add styleGuideIds to AI Translation requests). Both request models and API mock fixtures/tests already cover the field, so I will not open a duplicate PR. Maintainers can likely close this issue as completed by #379. I am stepping back from it.andrii-bodnar commentedon Sep 5, 2026
@77cjj Thanks for looking into this! The same issue was created by mistake.