Skip to content

spec: add translation_memory resource and missing v3/languages/resour…#374

Merged
lilkraftwerk merged 2 commits into
mainfrom
spec/v3-languages-enums-match-live
Jun 18, 2026
Merged

spec: add translation_memory resource and missing v3/languages/resour…#374
lilkraftwerk merged 2 commits into
mainfrom
spec/v3-languages-enums-match-live

Conversation

@lilkraftwerk

Copy link
Copy Markdown
Contributor

What

GET /v3/languages and GET /v3/languages/resources had drifted from the live API. This extends three enums to match what api.deepl.com actually returns:

  • resource query parameter enum (/v3/languages): add translation_memory
  • /v3/languages/resources resource-name enum: add translation_memory
  • /v3/languages/resources feature-name enum: add transcription, translated_speech, spoken_terms, translation_memory

No API behavior change. This only aligns the published spec with the responses the live API already serves.

Evidence (live api.deepl.com)

translation_memory is a valid resource the current spec enum rejects:

$ curl '.../v3/languages?resource=translation_memory'
[
  { "lang": "de", "name": "German", "status": "stable",
    "usable_as_source": true, "usable_as_target": true, "features": {} },
  { "lang": "de-DE", "name": "German", "status": "stable",
    "usable_as_source": false, "usable_as_target": true, "features": {} },
  ...
]

/v3/languages/resources returns feature names not in the current enum (voice's spoken_terms / transcription / translated_speech, plus translation_memory as a resource):

$ curl '.../v3/languages/resources'
[
  ...
  { "name": "voice", "features": [
      { "name": "auto_detection",    "needs_source_support": true },
      { "name": "formality",         "needs_target_support": true },
      { "name": "glossary",          "needs_source_support": true, "needs_target_support": true },
      { "name": "spoken_terms",      "needs_source_support": true },
      { "name": "transcription",     "needs_source_support": true },
      { "name": "translated_speech", "needs_target_support": true }
  ] },
  { "name": "translation_memory", "features": [] }
]

Notes

  • YAML only; openapi.json is regenerated by the workflow.

Lucas Mathis and others added 2 commits June 18, 2026 16:57
…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.
@lilkraftwerk lilkraftwerk merged commit 4a90930 into main Jun 18, 2026
1 of 2 checks passed
@lilkraftwerk lilkraftwerk deleted the spec/v3-languages-enums-match-live branch June 18, 2026 15:04
@mintlify

mintlify Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
deepl-c950b784 🔴 Failed Jun 18, 2026, 3:15 PM

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

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