spec: add translation_memory resource and missing v3/languages/resour…#374
Merged
Conversation
…ces feature names GET /v3/languages and /v3/languages/resources lagged the live API: - resource enum (query param + /resources response) was missing translation_memory - /resources feature-name enum was missing transcription, translated_speech, spoken_terms, translation_memory Extend all three enums to match what api.deepl.com actually returns. YAML only; openapi.json is regenerated by the workflow.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
GET /v3/languagesandGET /v3/languages/resourceshad drifted from the live API. This extends three enums to match whatapi.deepl.comactually returns:resourcequery parameter enum (/v3/languages): addtranslation_memory/v3/languages/resourcesresource-name enum: addtranslation_memory/v3/languages/resourcesfeature-name enum: addtranscription,translated_speech,spoken_terms,translation_memoryNo API behavior change. This only aligns the published spec with the responses the live API already serves.
Evidence (live api.deepl.com)
translation_memoryis a valid resource the current spec enum rejects:/v3/languages/resourcesreturns feature names not in the current enum (voice'sspoken_terms/transcription/translated_speech, plustranslation_memoryas a resource):Notes
openapi.jsonis regenerated by the workflow.