We set article status badges through API v3 (PATCH /v3/articles/{id}/settings with status_indicator), and it works well. The Custom badge is the exception: its label is a localization variable, and as far as we can tell, no API can read or change it. GET /v3/projects/{project_id}/localization-variables returns a 404.

So when we set a badge to custom through the API, we can't check what readers will actually see without opening the portal.

Could you add v3 endpoints to list and update localization variables, per language? Even read-only access to the status badge labels would help.