Smartling REST API Reference

Name: Smartling REST API Reference API
Brand: Smartling REST API Reference
Availability: InStock

✓ Official Vendor SpecHR recruitingRecruiting Atsnone109 EndpointsREST

For Agents

Programmatically authenticate, refresh access token. Covers 109 operations.

Use for: I need to authenticate, I want to refresh access token, Search for projects, Find all project details

Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.

Before you begin using the Smartling APIs, we recommend going through our [Developer documentation](https://help.smartling.com/hc/en-us/categories/1260801686149). The API exposes 109 endpoints.

Jentic One on Github View OpenAPI Document

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%2Fsmartling.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%2Fsmartling.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.

Authenticate

Refresh access token

List projects

Get project details

Add a new target locale

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.

★ HR and Recruiting Operations

Use the Smartling REST API Reference to perform hr recruiting operations programmatically. The API provides 109 endpoints covering core functionality including authenticate, refresh access token, list projects.

Call POST /auth-api/v2/authenticate to authenticate

Automated Authentication Management

Automate authentication operations by combining multiple Smartling REST API Reference endpoints. Agents can refresh access token and then list projects in a single workflow.

Call POST /auth-api/v2/authenticate/refresh to refresh access token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Smartling REST API Reference endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.

Search Jentic for 'authenticate', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

109 endpoints — before you begin using the smartling apis, we recommend going through our [developer documentation](https://help.

METHOD

PATH

DESCRIPTION

POST

/auth-api/v2/authenticate

Authenticate

POST

/auth-api/v2/authenticate/refresh

Refresh access token

GET

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

List projects

GET

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

Get project details

POST

/projects-api/v2/projects/{projectId}/targetLocales

Add a new target locale

POST

/projects-api/v2/projects/{projectId}/copy

Copy an existing project

GET

/projects-api/v2/projects/{projectId}/copy/{processUid}

Get the status of the project copy request

GET

/locales-api/v2/dictionary/locales

List locales

POST

/auth-api/v2/authenticate

Authenticate

POST

/auth-api/v2/authenticate/refresh

Refresh access token

GET

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

List projects

GET

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

Get project details

POST

/projects-api/v2/projects/{projectId}/targetLocales

Add a new target locale

POST

/projects-api/v2/projects/{projectId}/copy

Copy an existing project

GET

/projects-api/v2/projects/{projectId}/copy/{processUid}

Get the status of the project copy request

GET

/locales-api/v2/dictionary/locales

Why Jentic?

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

Setup

Wiring Smartling by hand means calling its auth-api to exchange credentials for a token, refreshing it, and managing retries against api.smartling.com yourself. Through Jentic you install once, import the Smartling REST API from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Smartling puts the project id in the URL path (/projects-api/v2/projects/{projectId}/...), so a rule can pin your agent to one project: it can read that project and add target locales. You choose the operations it may call, so a project copy is not included unless you add it.

Credential isolation

Your Smartling credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get a project's details' or 'add a target locale', 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 Reference use?

The Smartling REST API Reference uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I authenticate with the Smartling REST API Reference?

Yes. Use the POST /auth-api/v2/authenticate endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Smartling REST API Reference?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I authenticate through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate'. Jentic returns the matching Smartling REST API Reference operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Smartling REST API Reference have?

The Smartling REST API Reference exposes 109 endpoints covering authentication, account & projects, locales operations.

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

Yes. Because Jentic One is self-hosted, your own rules decide which Smartling operations and credentials the agent may use. Smartling puts the project id in the URL path (/projects-api/v2/projects/{projectId}/...), so a rule can pin your agent to a single project and allow only the operations you choose, such as reading project details and adding target locales. Operations you do not grant, like copying a project, stay off limits until you explicitly add them.

Smartling REST API Reference

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