Skip to content

feat(API): Add translation_key_prefix and filter_by_prefix to async locale download#1210

Merged
Sven Dunemann (forelabs) merged 2 commits into
mainfrom
feat/async-downloads-api-key-filter
Jun 25, 2026
Merged

feat(API): Add translation_key_prefix and filter_by_prefix to async locale download#1210
Sven Dunemann (forelabs) merged 2 commits into
mainfrom
feat/async-downloads-api-key-filter

Conversation

@forelabs

Copy link
Copy Markdown
Member

Changes

  • Add translation_key_prefix and filter_by_prefix params to locale_downloads/create for parity with the sync locale download endpoint
  • Clarify filter_by_prefix description on both endpoints: it requires translation_key_prefix to be set

- Add translation_key_prefix and filter_by_prefix params to locale_downloads/create
  to match parity with the sync locale download endpoint
- Clarify filter_by_prefix description: requires translation_key_prefix to be set
@forelabs Sven Dunemann (forelabs) changed the title Add translation_key_prefix and filter_by_prefix to async locale download feat(API): Add translation_key_prefix and filter_by_prefix to async locale download Jun 25, 2026
@github-actions

github-actions Bot commented Jun 25, 2026

Copy link
Copy Markdown
Contributor

API changelog (oasdiff)

Doc-only edits (descriptions, examples) do not appear here.

2 changes: 0 error, 0 warning, 2 info
info	[new-optional-request-property] at doc/compiled.json
	in API POST /projects/{project_id}/locales/{locale_id}/downloads
		added the new optional request property `filter_by_prefix`

info	[new-optional-request-property] at doc/compiled.json
	in API POST /projects/{project_id}/locales/{locale_id}/downloads
		added the new optional request property `translation_key_prefix`

Custom metadata filters. Provide the name of the metadata field and the value to filter by. Only keys with matching metadata will be included in the download.
type: object
properties: {}
translation_key_prefix:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

we should probably extract these to a reference as they are repeated in multiple endpoints. I'll probably try to do it in a separate PR

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