Install Jentic One Beta

Connect the Smartling REST API Reference to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Smartling REST API Reference, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi-reference.smartling.com%2Fsmartling" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi-reference.smartling.com%2Fsmartling" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Smartling REST API Reference API.

Upload source files and track their translation status by locale

Download translated files for one or all target locales

Create, authorize, schedule, and close translation jobs

Add and remove files or strings within a job

Estimate translation cost and fuzzy-match savings for a job

GET STARTED

Start building with Smartling REST API Reference API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Smartling REST API Reference API for, with concrete tasks.

★ Automated Content Localization

A content agent uploads new source files to Smartling whenever a product page changes, then tracks each locale's status until translations are ready. It uploads the file, polls the per-locale status, and downloads completed translations. Through Jentic the agent finds the upload and download operations and calls them scoped to the right project.

Upload a source file, wait for a target locale to complete, and download the translated file

Translation Job Orchestration

A localization manager agent groups strings and files into a translation job, authorizes it, and schedules delivery. It creates the job, adds content, and authorizes it so vendors can begin. Progress and completion dates let the agent report status back to stakeholders.

Create a translation job, add files, and authorize it so translation can start

Cost Estimation Before Commit

Before authorizing work, a finance-aware agent estimates the cost and fuzzy-match savings for a job. It requests the cost and fuzzy reports for the job and reads the totals once ready. This lets a team approve budgets before translation begins.

Request a cost estimate for a translation job and return the projected total

String and Context Management

A developer agent pushes source strings and visual context so translators see where text appears. It uploads strings, attaches context, and tags strings for later filtering. Better context reduces translation errors and rework.

Upload source strings, attach visual context, and tag them for a release

Key Endpoints

109 endpoints — the smartling rest api manages software and content localization across projects, files, and target locales.

METHOD

PATH

DESCRIPTION

POST

/auth-api/v2/authenticate

Exchange credentials for an access token

GET

/accounts-api/v2/accounts/{accountUid}/projects

List projects in an account

POST

/files-api/v2/projects/{projectId}/file

Upload a source file for translation

GET

/files-api/v2/projects/{projectId}/files/list

List files in a project

POST

/files-api/v2/projects/{projectId}/locales/{localeId}/file/get-translations

Download translations for a locale

POST

/jobs-api/v3/projects/{projectId}/jobs

Create a translation job

POST

/jobs-api/v3/projects/{projectId}/jobs/{translationJobUid}/authorize

Authorize a translation job

POST

/auth-api/v2/authenticate

Exchange credentials for an access token

GET

/accounts-api/v2/accounts/{accountUid}/projects

List projects in an account

POST

/files-api/v2/projects/{projectId}/file

Upload a source file for translation

GET

/files-api/v2/projects/{projectId}/files/list

List files in a project

POST

/files-api/v2/projects/{projectId}/locales/{localeId}/file/get-translations

Download translations for a locale

POST

/jobs-api/v3/projects/{projectId}/jobs

Create a translation job

POST

/jobs-api/v3/projects/{projectId}/jobs/{translationJobUid}/authorize

Authorize a translation job

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Smartling by hand means exchanging credentials for a bearer token against api.smartling.com, refreshing it, and threading it through every file and job call yourself. Through Jentic you install once, import Smartling from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Smartling's operations are scoped to a project, so a rule limits your agent to a specific project and to the operations it needs, such as uploading files and reading status. You choose which operations it may call, so authorizing or deleting a job is included only when you add it.

Credential isolation

Your Smartling credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'upload a file for translation' or 'create a translation job', and Jentic returns the matching Smartling operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Smartling REST API Reference API through Jentic.

What authentication does the Smartling REST API use?

The Smartling REST API authenticates by exchanging your user identifier and secret at the authenticate endpoint for a bearer access token, which is then sent in the Authorization header. Through Jentic, those credentials are stored encrypted by your own Jentic One instance and injected at execution time, so they never enter the agent's prompt or logs.

How does file upload and translation work in the Smartling REST API?

You upload a source file to a project, and Smartling tracks its translation status per target locale. Once a locale is complete, you download the translated file for that locale. An agent can automate the loop: upload, poll status, and download when ready.

What are the rate limits for the Smartling REST API?

The OpenAPI spec does not specify rate limits for the Smartling REST API. Check the Smartling developer documentation at https://help.smartling.com for current limits, and back off when you receive a 429 response.

How do I create a translation job through Jentic?

Search Jentic for 'create a translation job', import Smartling from the API Directory, and store your credentials once. Jentic returns the job-creation operation with its project and job parameters so your agent can call it directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I estimate translation cost before authorizing a job?

Yes. The Smartling REST API generates cost and fuzzy-match reports for a job, so an agent can request the estimate and read the projected total before authorizing the work. This lets a team approve budgets before translation begins.

Can I limit what my agent is allowed to do with the Smartling REST API?

Yes. Operations are scoped to a project, so you write a rule that lets the agent act only within a specific project and only with the operations it needs, such as uploading files and reading status. Because Jentic One is self-hosted, those rules and the audit log of every call stay on your own infrastructure.

Is there a Smartling REST API MCP server?

You do not need an MCP server to give your agent the Smartling REST API. Jentic connects it directly from the API Directory: import it, store your credentials once, and your agent can upload files, manage jobs, and download translations. That also keeps your agent's context free of an extra server's tool definitions.

Api Reference Smartling Smartling REST API Reference

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer109 EndpointsREST

For Agents

Upload source files, manage translation jobs and locales, download translated content, estimate cost, and drive localization workflows per project.

Use for: I want to upload a source file for translation, Check the translation status of a file for a locale, Download the translated file for a target locale, Create a translation job and add files to it

Not supported: Manages localization of files, strings, and jobs. Does not perform machine translation directly beyond routing, and does not manage billing or account provisioning.

The Smartling REST API manages software and content localization across projects, files, and target locales. It uploads source files, tracks translation status, and downloads translated content per locale, while translation jobs group work and move it through authorization, scheduling, and completion. Beyond files and jobs, it exposes source strings, context uploads and matching, cost and fuzzy estimates, tags, and machine-translation routing. Operations are scoped to a project within an account, so agents drive a full localization workflow programmatically.

Jentic One on Github View OpenAPI Document

Connect the Smartling REST API Reference to your agent

Capabilities

Start building with Smartling REST API Reference API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Api Reference Smartling Smartling REST API Reference