List language translations

List language translations

List the translation rows of one customiser language, in catalogue order — the order the merchant admin editor presents them in, which groups related copy together and stays stable across pages. Every row carries two phases. The `draft_*` members are what a merchant or an AI translation is working on; the `published_*` members are what the storefront serves. Only publishing the language promotes one to the other. `source_text` is the text that this row is translated from, as the catalogue last stored it. When the customiser has an authoring language, option, selection, setting, letter-part and form text carries the authoring language's text. For an interface label, it is the published text of the language's `source_language_code` when that language has published text for the key. Otherwise, it is the published text of the default language, or its built-in text when that is blank. A promoted default also follows its `source_language_code`. A default with no `source_language_code` uses its own text. With no authoring language, every row carries the catalogue text. For option and form text, that is the customiser's own text. For interface labels, it is the published text of the default language. For such a customiser, the merchant admin can show the current wording of the source language instead, drafts included. `draft_stale` and `published_stale` are true when the value is filled but its source changed after the value was written. The value still serves and still publishes. It no longer matches the text it was translated from. `retired` rows are keys whose copy no longer exists. They are kept for history, excluded from publishing and from AI work, and refused on write — use `filter[retired]=false` to leave them out entirely. The operation is read-only, has no side effects, and is always safe to retry. Requires the `customisers:read` scope. A 404 problem with code `resource_not_found` means the customiser or the language does not exist on the store your API key belongs to. A 401 problem means the key is missing, invalid, or expired; a 403 problem with code `insufficient_scope` means the key lacks `customisers:read`; a 422 problem means an unknown query parameter, an unknown filter, or an invalid cursor; a 429 problem means too many requests — wait `retry_after` seconds, then retry.