Secure API Integrations let you connect VideoTranslatorAI’s Text Translation projects directly to your own systems, with enterprise-grade security and compliance. This ensures sensitive multilingual content is protected at every stage—without compromising speed or performance.

Learn more on our marketing page →

Overview

Currently available for Text Translation projects, Secure API Integrations provide:

  • End-to-end encryption for all API calls, both in transit and at rest.
  • Granular access controls to protect translation data and project resources.
  • Support for major global data protection and compliance standards.
  • Safe interoperability with enterprise systems and third-party applications.

Key Capabilities

  • SHA-256 encryption for API traffic and stored content
  • API key authentication
  • Role-based access control for API endpoints
  • Audit logs for integration activity tracking
  • Region-specific data hosting

Best Practices

  • Rotate API keys regularly and disable unused credentials.
  • Monitor audit logs for unusual API activity.
  • Pair with Manage Access and Teams settings for maximum protection.

How to Use Secure API Integration

Currently supported endpoint: Text Translation API – POST /v1/translate

Text Translation API – POST /v1/translate

The translate endpoint creates a translation project based on a predefined Text Project Template and returns the translated text for the specified target languages.

Endpoint 

POST https://api.videotranslator.ai/v1/translate

Headers

Header Type Required Description
x-api-key string Yes API key to authenticate the request.
Content-Type string Yes Must be application/json.

Request Body

The body must be a JSON object with the folliwing fields:

Field Type Required Description
textProjectTemplateId string Yes The ID of the text project template. Determines the required structure of the sourcePayload.
sourcePayload object Yes Key-value pairs containing the source text. Fields depend on the template schema.
targetLanguages string[] Yes Array of ISO language codes for the desired target translations. Example: ["id", "fr"].

Example Request Body

{
  "textProjectTemplateId": "1d1de4c2-0637-4b71-b5a5-c3e156de3288",
  "sourcePayload": {
    "title": "Severe Thunderstorm Warning",
    "date": "18/08/2025",
    "category": "Advice",
    "warning_message": "A severe thunderstorm is expected in the region. Strong winds and heavy rainfall likely.",
    "information": "Power outages and flash flooding may occur. Stay indoors and avoid travel.",
    "instructions": [
      {
        "step": "Seek shelter immediately. Secure outdoor items."
      }
    ],
    "more_info": [
      "Visit the Bureau of Meteorology website or tune into local radio updates."
    ]
  },
  "targetLanguages": [
    "id"
  ]
}

Successful Response (200)

Field Type Description
success boolean Indicates if the request was successful.
message string Human-readable message describing the result.
data object[] Array of translated payloads, one for each requested target language.

Example Success Response

{
  "success": true,
  "message": "Text Project created successfully",
  "data": [
    {
      "title": "Severe Thunderstorm Warning",
      "date": "18/08/2025",
      "category": "Advice",
      "warning_message": "Peringatan badai petir hebat diperkirakan terjadi di wilayah ini. Angin kencang dan hujan lebat kemungkinan besar terjadi.",
      "information": "Pemadaman listrik dan banjir bandang mungkin terjadi. Tetaplah di dalam rumah dan hindari perjalanan.",
      "instructions": [
        {
          "step": "Segera cari tempat berlindung. Amankan barang-barang di luar ruangan."
        }
      ],
      "more_info": [
        "Kunjungi situs web Biro Meteorologi atau dengarkan pembaruan radio lokal."
      ],
      "translatedLanguageCode": "id"
    }
  ]
}

Error Response (400 – Bad Request)

Returned when the payload does not match the expected template schema.

Field Type Description
success boolean Always false for errors.
message string Description of the error.
data object Contains validation errors.

Example Error Respones

{
  "success": false,
  "message": "Invalid payload for template",
  "data": {
    "errors": [
      {
        "path": "",
        "property": "instance",
        "message": "requires property 'warning_message'"
      }
    ]
  }
}

Notes

  • The template ID defines which fields are required in the sourcePayload. If a required field is missing, the API will return a validation error.
  • Certain fields (title, date, category) may be intended for context only and do not need translation.
  • The API supports multiple target languages by including additional ISO codes in the targetLanguages array.

Example for Multiple Target Language

"targetLanguages": ["id", "fr", "es"]

Example Workflow

Scenario: A government agency integrates VideoTranslatorAI into its secure incident reporting system.

  1. All API requests require an API key and are limited to designated IP addresses.
  2. All transmissions are encrypted with SHA-256.
  3. Glossaries and translation prompts are fetched via API for consistency.
  4. Access logs are reviewed monthly to ensure compliance.

Troubleshooting & FAQs

Q: Do secure integrations affect API speed?
A: No — encryption and authentication are optimised for minimal latency.

Q: Can I restrict API access by IP address?
A: Yes — enterprise plans support IP allowlists.

Q: How can I verify my integration is compliant with regulations?
A: Review our compliance documentation and run regular security audits using the provided API logs.

🔗 See Also