Skip to content

feat: Document translation memory management endpoints - #418

Open
BriannaDelgado wants to merge 3 commits into
mainfrom
add-translation-memory-crud-endpoints
Open

feat: Document translation memory management endpoints#418
BriannaDelgado wants to merge 3 commits into
mainfrom
add-translation-memory-crud-endpoints

Conversation

@BriannaDelgado

Copy link
Copy Markdown
Member

Add API reference pages for retrieving, listing segments, importing, exporting, deleting translation memories, and polling import/export jobs. Updates the OpenAPI spec, navigation, permission scopes, and release notes to match.

Add API reference pages for retrieving, listing segments, importing,
exporting, deleting translation memories, and polling import/export
jobs. Updates the OpenAPI spec, navigation, permission scopes, and
release notes to match.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated (UTC)
deepl-c950b784 🟢 Ready View Preview Aug 11, 2026, 1:54 PM

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


<Steps>
<Step title="Create the import job">
Send the file's name and size in bytes. The response returns the `job_id`, the `upload_url`, and the `expires_at` deadline for the upload.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we document what the max content length is?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just added here and also in the openapi specs

Comment thread api-reference/openapi.yaml Outdated
- downloaded
- failed
- expired
- unspecified

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we keep this? Is unspecified even a valid input? I assume not?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch - Claude got confused between the internal/customer-facing states. Just removed unspecified and downloaded.

Comment thread api-reference/openapi.yaml Outdated
enum:
- import
- export
- unspecified

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment here about unspecified

properties:
job_id:
description: The identifier of the job.
type: string

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In some places we also specify format: uuid for ID fields. Should we do the same here?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done 👍

Comment thread api-reference/openapi.yaml Outdated
- awaiting_input
- processing
- completed
- downloaded

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we keeping this as a status value?

Replaces "within DeepL's size limit for TMX imports" in both specs and
on the import page.

Co-Authored-By: Claude Opus 5 <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.

2 participants