Smartling

How to integrate Smartling with Webflow

Smartling is a localization tool that uses AI to translate text into different languages. You can integrate Smartling with Webflow using the official app, or through any of the methods listed below.

Use Webflow Connector for visual translation management

The Webflow Connector provides point-and-click translation management without coding. Connect your Webflow site to Smartling, select pages for translation, and manage translations through the Smartling dashboard. The connector handles page selection, content extraction, translation coordination, and publishing translated content back to Webflow.

Use this method when you need straightforward page translation without custom automation. The connector works for standard workflows where you translate complete pages through Smartling's visual interface.

Build with Webflow and Smartling REST API

Smartling's REST APIs provide custom translation workflows for Webflow CMS content. The File API submits content for translation, the Strings API manages individual translatable strings, and the Jobs API coordinates translation workflows. Monitor translation progress and manage content through structured API calls.

The Smartling API suite provides four APIs that handle different translation scenarios. The File API translates entire Webflow pages at once. The Strings API updates individual product descriptions without re-translating full pages. The Jobs API groups related content with shared deadlines across languages. The Context API uploads screenshots showing how text appears in your Webflow design.

Use the REST API when you need custom automation beyond standard page translation. This includes Webflow CMS collection synchronization, automated translation triggers based on content changes, or integration with existing development workflows.

Authentication and access management

All Smartling API requests require access tokens using OAuth authentication obtained through the Authentication API. Send your user identifier and token secret to POST /auth-api/v2/authenticate to receive an access token valid for 30 minutes. Include this token in all subsequent requests as Authorization: Bearer {accessToken}.

Access tokens expire after 30 minutes. Implementations should either refresh tokens proactively or handle authentication errors during long-running operations by re-authenticating and retrying failed requests.

Bulk content translation with the Files API

The File API handles translation of complete content files. This approach works for translating entire CMS collections or page content exported from Webflow.

File submission workflow:

• Upload content with POST /files-api/v2/projects/{projectId}/file. Include the file binary, unique fileUri identifier, fileType specification, and authorize boolean. Add optional localeIdsToAuthorize array for target locale codes.
• Monitor translation status through GET /files-api/v2/projects/{projectId}/file/status. This returns wordCount, stringCount, approvedStringCount, and completedStringCount metrics.
• Download completed translations via GET /files-api/v2/projects/{projectId}/locales/{localeId}/file. Set retrievalType to "published" to get only finalized content.
• List uploaded files using GET /files-api/v2/projects/{projectId}/files/list. Filter with uriMask patterns or lastUploadedAfter timestamps for incremental synchronization.

The fileUri parameter acts as the unique identifier across all file operations. Use consistent naming patterns like webflow/homepage-en.json to maintain content organization across translation cycles.

Update individual fields with the Strings API

The Strings API manages individual translatable strings without requiring full file re-uploads. This works for content that changes independently, such as product descriptions in CMS collections. Update specific strings in translation without modifying the entire collection structure.

String submission and retrieval:

• Add strings with POST /strings-api/v2/projects/{projectId}/strings. Send hashcode (unique identifier), stringText (source content), format ("plaintext" or "html"), and optional variant metadata.
• Retrieve translations via GET /strings-api/v2/projects/{projectId}/strings/translations. Include comma-separated hashcodes parameter and required targetLocaleId parameter.
• Check translation status through GET /strings-api/v2/projects/{projectId}/strings/status. Use hashcodes parameter to monitor completion percentages and authorization states before publishing to Webflow.

Translation workflow coordination with the Jobs API

Jobs coordinate translation workflows where multiple target languages are managed together. Launch a new product page in three languages next Tuesday by creating a job that groups the page content, product descriptions, and navigation updates. Track completion across French, German, and Spanish before publishing all languages together.

Job creation and management:

• Create translation jobs with POST /jobs-api/v3/projects/{projectId}/jobs. Specify jobName, targetLocaleIds array, dueDate, and optional referenceNumber for external system correlation.
• Add content to jobs via POST /jobs-api/v3/projects/{projectId}/jobs/{jobUid}/file/add. This associates previously uploaded files with the translation batch.
• Monitor job progress through GET /jobs-api/v3/projects/{projectId}/jobs/{jobUid}. This returns per-locale completion metrics.
• Close completed jobs using POST /jobs-api/v3/projects/{projectId}/jobs/{jobUid}/close. This marks work complete and triggers delivery workflows.

What you can build

Integrating Smartling with Webflow creates translation workflows that reduce manual coordination overhead.

• Translated product catalogs: Send Webflow CMS collection content through the Files API or Strings API, monitor completion with the Jobs API, and publish synchronized updates across locales
• Localized component libraries: Submit Webflow component text through the Strings API with context, track translation progress, and update Webflow instances with completed translations
• Coordinated content launches: Group related Webflow content into translation jobs with deadlines, monitor per-language completion, and trigger publishing when all languages complete
• Automated translation workflows: Build custom integrations that detect CMS collection changes, submit content for translation automatically, and update localized versions when translations complete

‍