---
title: "Add Translation"
method: POST
path: "/v1/{workspace}/translation/content/{locale_file}/"
---

# Add Translation

`POST /v1/{workspace}/translation/content/{locale_file}/`

Upload or create a new translation file. The file content should be valid JSON following the translation file structure.

## Path parameters

- `workspace` string, required
- `locale_file` string, required

## Request body

- object
  - `locale` string, required — Locale file name (e.g., "fr.json", "es-MX.json", "auth.en.json")
  - `content` object, required — Translation key-value pairs in JSON format

## Response `201`

Translation file successfully updated

- object
  - `filename` string — Name of the translation file
  - `locale` string — Locale code for the translation file
  - `locale_name` string — Human-readable name of the locale
  - `namespace` string, nullable — Namespace for the translation file, if any. Namespace can be used to group translations by feature or module.
  - `action` 'added' | 'updated' | 'deleted' | 'unchanged' — action done in the version compared to last commit.
  - `updated_at` string, date-time — When the translation file was last updated
  - `content` object — Translation key-value pairs

## Other responses

- `400` — Invalid translation format
- `401` — Authentication failed
- `404` — Resource not found

---

[API](https://skmtc.net/suprsend/apis/suprsend-api.md) · [All operations](https://skmtc.net/suprsend/apis/suprsend-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/suprsend/suprsend-api/revisions/a686fddb4e0c/schema)