> ## Documentation Index > Fetch the complete documentation index at: https://novu-c5de82d9-docs-homepage-redesign.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Upload translation files > Upload translation files using the Novu REST API. Requires your environment secret key in the Authorization header. ## OpenAPI ````yaml POST /v2/translations/upload openapi: 3.0.0 info: title: Novu API description: >- Novu REST API. Please see https://docs.novu.co/api-reference for more details. version: 3.15.0 contact: name: Novu Support url: https://discord.gg/novu email: support@novu.co termsOfService: https://novu.co/terms license: name: MIT url: https://opensource.org/license/mit servers: - url: https://api.novu.co - url: https://eu.api.novu.co security: - secretKey: [] tags: - name: Events description: >- Events represent a change in state of a subscriber. They are used to trigger workflows, and enable you to send notifications to subscribers based on their actions. externalDocs: url: https://docs.novu.co/workflows - name: Subscribers description: >- A subscriber in Novu represents someone who should receive a message. A subscriber's profile information contains important attributes about the subscriber that will be used in messages (name, email). The subscriber object can contain other key-value pairs that can be used to further personalize your messages. externalDocs: url: https://docs.novu.co/subscribers/subscribers - name: Topics description: >- Topics are a way to group subscribers together so that they can be notified of events at once. A topic is identified by a custom key. This can be helpful for things like sending out marketing emails or notifying users of new features. Topics can also be used to send notifications to the subscribers who have been grouped together based on their interests, location, activities and much more. externalDocs: url: https://docs.novu.co/subscribers/topics - name: Integrations description: >- With the help of the Integration Store, you can easily integrate your favorite delivery provider. During the runtime of the API, the Integrations Store is responsible for storing the configurations of all the providers. externalDocs: url: https://docs.novu.co/platform/integrations/overview - name: Workflows description: >- All notifications are sent via a workflow. Each workflow acts as a container for the logic and blueprint that are associated with a type of notification in your system. externalDocs: url: https://docs.novu.co/workflows - name: Messages description: >- A message in Novu represents a notification delivered to a recipient on a particular channel. Messages contain information about the request that triggered its delivery, a view of the data sent to the recipient, and a timeline of its lifecycle events. Learn more about messages. externalDocs: url: https://docs.novu.co/workflows/messages - name: Environments description: >- Environments allow you to manage different stages of your application development lifecycle. Each environment has its own set of API keys and configurations, enabling you to separate development, staging, and production workflows. externalDocs: url: https://docs.novu.co/platform/environments - name: Layouts description: Layouts are reusable wrappers for your email notifications. externalDocs: url: https://docs.novu.co/platform/workflow/layouts - name: Translations description: Used to localize your notifications to different languages. externalDocs: url: https://docs.novu.co/platform/workflow/advanced-features/translations - name: Domains description: Used to manage your inbound email domains. externalDocs: url: https://docs.novu.co/platform/domains externalDocs: description: Novu Documentation url: https://docs.novu.co paths: /v2/translations/upload: post: tags: - Translations summary: Upload translation files description: >- Upload one or more JSON translation files for a specific workflow. Files name must match the locale, e.g. en_US.json. Supports both "files" and "files[]" field names for backwards compatibility. operationId: TranslationController_uploadTranslationFiles parameters: - name: idempotency-key in: header description: A header for idempotency purposes required: false schema: type: string requestBody: required: true content: multipart/form-data: schema: type: object properties: resourceId: type: string description: >- The resource ID to associate localizations with. Accepts identifier or slug format example: welcome-email resourceType: type: string enum: - workflow - layout description: The resource type to associate localizations with files: type: array items: type: string format: binary description: >- One or more JSON translation files. Filenames must match locale format (e.g., en_US.json, fr_FR.json). Field name can be "files" or "files[]". required: - resourceId - resourceType - files responses: '200': description: Upload results content: application/json: schema: $ref: '#/components/schemas/UploadTranslationsResponseDto' security: - secretKey: [] - secretKey: [] x-codeSamples: - lang: php label: PHP source: >- declare(strict_types=1); require 'vendor/autoload.php'; use novu; use novu\Models\Operations; $sdk = novu\Novu::builder() ->setSecurity( 'YOUR_SECRET_KEY_HERE' ) ->build(); $requestBody = new Operations\TranslationControllerUploadTranslationFilesRequestBody( resourceId: 'welcome-email', resourceType: Operations\ResourceType::Workflow, files: [], ); $response = $sdk->translations->upload( requestBody: $requestBody ); if ($response->uploadTranslationsResponseDto !== null) { // handle response } - lang: python label: Python source: |- import novu_py from novu_py import Novu with Novu( secret_key="YOUR_SECRET_KEY_HERE", ) as novu: res = novu.translations.upload(request_body={ "resource_id": "welcome-email", "resource_type": novu_py.TranslationControllerUploadTranslationFilesResourceType.WORKFLOW, "files": [], }) # Handle response print(res) - lang: go label: Go source: "package main\n\nimport(\n\t\"context\"\n\t\"github.com/novuhq/novu-go/v3\"\n\t\"github.com/novuhq/novu-go/v3/models/operations\"\n\t\"log\"\n)\n\nfunc main() {\n ctx := context.Background()\n\n s := v3.New(\n v3.WithSecurity(\"YOUR_SECRET_KEY_HERE\"),\n )\n\n res, err := s.Translations.Upload(ctx, operations.TranslationControllerUploadTranslationFilesRequestBody{\n ResourceID: \"welcome-email\",\n ResourceType: operations.ResourceTypeWorkflow,\n Files: []operations.Files{},\n }, nil)\n if err != nil {\n log.Fatal(err)\n }\n if res.UploadTranslationsResponseDto != nil {\n // handle response\n }\n}" - lang: typescript label: TypeScript source: |- import { Novu } from "@novu/api"; const novu = new Novu({ secretKey: "YOUR_SECRET_KEY_HERE", }); async function run() { const result = await novu.translations.upload({ resourceId: "welcome-email", resourceType: "workflow", files: [], }); console.log(result); } run(); - lang: csharp label: Csharp (SDK) source: >- using Novu; using Novu.Models.Components; using Novu.Models.Requests; using System.Collections.Generic; var sdk = new NovuSDK(secretKey: "YOUR_SECRET_KEY_HERE"); var res = await sdk.Translations.UploadAsync(requestBody: new TranslationControllerUploadTranslationFilesRequestBody() { ResourceId = "welcome-email", ResourceType = Novu.Models.Requests.ResourceType.Workflow, Files = new List() {}, }); // handle response components: schemas: UploadTranslationsResponseDto: type: object properties: totalFiles: type: number description: Total number of files processed example: 3 successfulUploads: type: number description: Number of files successfully uploaded example: 2 failedUploads: type: number description: Number of files that failed to upload example: 1 errors: description: List of error messages for failed uploads example: - 'Invalid JSON in file: es-ES.json' type: array items: type: string required: - totalFiles - successfulUploads - failedUploads - errors securitySchemes: secretKey: type: apiKey name: Authorization in: header description: >- API key authentication. Allowed headers-- "Authorization: ApiKey ". x-speakeasy-example: YOUR_SECRET_KEY_HERE ````