Set language on the schedule — 33 supported locale codes, defaulting to en
The schedule's language field is the locale a report's headings, metric names, and standard copy resolve to. It is chosen per schedule, not per tenant, so one client can receive English and another Portuguese from the same workspace.
The list#
33 codes are supported: en, es, fr, de, pt, pt-BR, it, nl, sv, da, no, fi, pl, cs, ro, hu, tr, ru, uk, el, vi, id, th, hi, bn, zh-CN, zh-TW, ja, ko, ar, he, fa, ur. Scripts with directionality (for example ar, he, fa, ur) carry their right-to-left direction with the locale.
Set and change#
Pass language in POST /v1/clients/:id/schedules (defaults to en) or PUT /v1/clients/:id/schedules/:scheduleId. There is no picker UI — your integration stores the audience's preference on the schedule row and generation reads it back per run.
Unknown codes#
A code outside the supported list does not fail the save; at message-resolution time it falls back to the first supported locale (English), so a typo degrades to readable defaults instead of breaking delivery. Pick from the list above to be deliberate (see How translation resolves).