mcp

List Untranslated Keys

Return keys that DON'T yet have a valid translation in language_code.

A key is considered "untranslated" in the target language when ANY of:

  • no translation row exists for (key, language) at all
  • row exists but value is empty
  • row exists but status == "missing"

Keys whose SOURCE-language value is empty/absent are EXCLUDED by default (reported separately as source_missing) — they are a source-data gap, not an untranslated target. Pass include_source_missing=true to include them.

The response is intentionally compact (no translations[] array) so Claude can scan a long list and propose translations for each entry using source_value as the input.

get/v1/mcp/projects/{project_id}/untranslated-keys

Request

  • Base URL: https://api.sonenta.dev
  • URL: https://api.sonenta.dev/v1/mcp/projects/{project_id}/untranslated-keys
  • Auth: none declared

Path parameters

project_idstring required

Query parameters

language_codestring required

Required: BCP-47 target language code (e.g. fr).

namespacestring nullable

Filter by namespace slug

cursorstring nullable
limitinteger
include_glossary_hintsboolean

Attach per-key glossary_hints[]: glossary rules matched in the source string.

include_source_missingboolean

By default keys whose SOURCE value is empty/absent are EXCLUDED (untranslated requires a source to translate). Set true to include them; their count is always reported as source_missing.

Response

Successful Response

cursor_nextstring nullable required
totalinteger required
source_missinginteger

Changes

No recorded changes to this operation across all 1 revision of this API.