Skip to content

docs: document show_translation_memory_matches on the translate endpoint - #441

Open
lawl-dev wants to merge 1 commit into
mainfrom
docs/translation-memory-matches
Open

lawl-dev wants to merge 1 commit into
mainfrom
docs/translation-memory-matches

Conversation

@lawl-dev

Copy link
Copy Markdown
Contributor

Documents the new show_translation_memory_matches parameter on POST /v2/translate.

  • Request: show_translation_memory_matches (JSON and form), with the schema component ShowTranslationMemoryMatches.
  • Response: translations[].customizations.translation_memory_matches with translation_memory_id, segment_id, match_score and text_ranges.
  • Guide: a new step in "Using Translation Memories" showing how to tell which segments came from the translation memory, including the model-judgment caveat and the tag_handling limitation.

openapi.json regenerated with yq. The backend change is rolling out to selected accounts first, which the docs state.

🤖 Generated with Claude Code

@mintlify

mintlify Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
deepl-c950b784 🟢 Ready View Preview Sep 16, 2026, 7:53 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

The parameter reports which translation memory segments were integrated
into each translated text and where they appear. Adds the request
parameter, the response shape under customizations, and a tutorial step.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
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

Successfully merging this pull request may close these issues.

1 participant