The Crowdin API adds organization-level concordance search endpoints that search across all accessible glossaries and translation memories (the existing concordance endpoints are project-scoped):
- Concordance search in Glossaries —
POST /glossaries/concordance (api.glossaries.concordance.post). Request body: sourceLanguageId (string, required), targetLanguageId (string, required), expressions (array of strings, required).
- Concordance search in TMs —
POST /tms/concordance (api.tms.concordance.post). Request body: sourceLanguageId (string, required), targetLanguageId (string, required), autoSubstitution (boolean, required), minRelevant (integer, required), expressions (array of strings, required).
On crowdin.com both request forms additionally accept an optional nullable userId (integer); this field does not exist in Crowdin Enterprise. Responses reuse the existing concordance result models.
Client libraries should add these organization-level methods alongside the existing project-scoped concordance search.
References:
The Crowdin API adds organization-level concordance search endpoints that search across all accessible glossaries and translation memories (the existing concordance endpoints are project-scoped):
POST /glossaries/concordance(api.glossaries.concordance.post). Request body:sourceLanguageId(string, required),targetLanguageId(string, required),expressions(array of strings, required).POST /tms/concordance(api.tms.concordance.post). Request body:sourceLanguageId(string, required),targetLanguageId(string, required),autoSubstitution(boolean, required),minRelevant(integer, required),expressions(array of strings, required).On crowdin.com both request forms additionally accept an optional nullable
userId(integer); this field does not exist in Crowdin Enterprise. Responses reuse the existing concordance result models.Client libraries should add these organization-level methods alongside the existing project-scoped concordance search.
References: