canonical: https://jentic.com/apis/simplelocalize.io/simplelocalize

# SimpleLocalize API

Swagger documentation for SimpleLocalize API. The API exposes 49 endpoints secured with apiKey authentication.

## For AI agents

Programmatically create project, list projects. Covers 49 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Create project
- List projects
- Import translations from file
- Get all environments
- Publish translations to given environment

## Use cases

### Developer Tools Operations

Use the SimpleLocalize API to perform developer tools operations programmatically. The API provides 49 endpoints covering core functionality including create project, list projects, create auto-translation jobs.

Example prompt: Call POST `/api/v2/projects` to create project

### Automated Translation keys Management

Automate translation keys operations by combining multiple SimpleLocalize API endpoints. Agents can list projects and then create auto-translation jobs in a single workflow.

Example prompt: Call GET `/api/v2/projects` to list projects, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SimpleLocalize API 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 apiKey tokens manually.

Example prompt: Search Jentic for 'create project', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/v2/projects` | Create project |
| GET | `/api/v2/projects` | List projects |
| POST | `/api/v2/jobs/auto-translate` | Create auto-translation jobs |
| POST | `/api/v2/import` | Import translations from file |
| POST | `/api/v2/environments` | Create a new environment |
| GET | `/api/v2/environments` | Get all environments |
| POST | `/api/v2/environments/{environmentKey}/publish` | Publish translations to given environment |
| POST | `/api/v1/translation-keys` | Create translation key |

## Key resources

- **Translation keys** — Project translation key management endpoints
- **Hosting** — Translation Hosting management endpoints
- **Activity** — Project activity
- **Projects** — Projects management endpoints
- **Tags** — Project tags management endpoints

## Why Jentic

- **Setup:** Wiring SimpleLocalize by hand means picking the right token style, its personal access token in the Authorization header or the project token in the X-SimpleLocalize-Token header, and threading that through every translation-key and publish call yourself. Through Jentic you install once, import SimpleLocalize from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** SimpleLocalize puts the environment key in the URL path (`/api/v2/environments/{environmentKey}/publish`), so a rule can pin your agent to one environment: it can publish and read there and nothing else. You choose the operations it may call, so project creation or an import that overwrites keys is not included unless you add it.
- **Credential handling:** Your SimpleLocalize token 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.
- **Discovery method:** Agents search Jentic by intent such as 'create a project' or 'auto-translate strings', and Jentic returns the matching SimpleLocalize operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the SimpleLocalize API use?

The SimpleLocalize API uses an API key passed in the `Authorization` header. 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 create project with the SimpleLocalize API?

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

### What are the rate limits for the SimpleLocalize API?

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 create project through Jentic?

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

### How many endpoints does the SimpleLocalize API have?

The SimpleLocalize API exposes 49 endpoints covering translation keys, hosting, activity operations.

### Can I limit what my agent is allowed to do with the SimpleLocalize API?

Yes. Jentic One runs self-hosted, so your own rules decide which SimpleLocalize operations and which token your agent may use. Because the environment key sits in the URL path (`/api/v2/environments/{environmentKey}/publish`), you can pin the agent to a single environment and let it publish and read translations there and nothing else. Operations you do not grant, such as creating projects with POST `/api/v2/projects` or running an import that overwrites keys, stay off limits.