canonical: https://jentic.com/apis/poeditor.com/poeditor

# Poeditor API V2

Connect your software to POEditor with this simple API. The API exposes 25 endpoints.

## For AI agents

Programmatically returns the list of projects owned by user., returns projects details. Covers 25 operations.

## Scope

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

## Capabilities

- Returns the list of projects owned by user.
- Creates a new project. Returns project details (if successful).
- Updates project settings (name, description, reference language, fallback langua
- Deletes the project from the account. You must be the owner of the project.
- Syncs your project with the array you send (terms that are not found in the JSON

## Use cases

### Developer Tools Operations

Use the API V2 to perform developer tools operations programmatically. The API provides 25 endpoints covering core functionality including returns the list of projects owned by user., returns projects details, creates a new project. returns project details (if successful)..

Example prompt: Call POST `/projects/list` to returns the list of projects owned by user.

### Automated Contributors Management

Automate contributors operations by combining multiple API V2 endpoints. Agents can returns projects details and then creates a new project. returns project details (if successful). in a single workflow.

Example prompt: Call POST `/projects/view` to returns projects details, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API V2 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.

Example prompt: Search Jentic for 'returns the list of projects owned by user.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/projects/list` | Returns the list of projects owned by user. |
| POST | `/projects/view` | Returns projects details |
| POST | `/projects/add` | Creates a new project. Returns project details (if successful). |
| POST | `/projects/update` | Updates project settings (name, description, reference language, fallback langua |
| POST | `/projects/delete` | Deletes the project from the account. You must be the owner of the project. |
| POST | `/projects/upload` | Updates terms / translations - No more than one request every 20 seconds. |
| POST | `/projects/sync` | Syncs your project with the array you send (terms that are not found in the JSON |
| POST | `/projects/export` | Returns the link of the file (expires after 10 minutes). The settings inherited |

## Key resources

- **Contributors** — Operations related to Contributors
- **Languages** — Operations related to Languages
- **Projects** — Operations related to Projects
- **Terms** — Operations related to Terms
- **Translations** — Operations related to Translations

## Why Jentic

- **Setup:** Wiring API V2 by hand means posting your POEditor API token in each form-encoded request to api.poeditor.com/v2 and selecting the right project operation yourself. Through Jentic you install once, import API V2 from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** API V2 identifies projects through the request body rather than pinning one in the URL path, so scope the agent to the operations it needs, such as listing or viewing projects. You choose that set, so destructive operations like deleting a project are included only if you add them while a read-only agent keeps just the list and view operations.
- **Credential handling:** Your POEditor API 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 'list projects owned by the user' or 'export a project', and Jentic returns the matching API V2 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 API V2 use?

The API V2 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 returns the list of projects owned by user. with the API V2?

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

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

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 returns the list of projects owned by user. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns the list of projects owned by user.'. Jentic returns the matching API V2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The API V2 exposes 25 endpoints covering contributors, languages, projects operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which POEditor operations and credentials the agent may use, and the API identifies each project in the request body rather than pinning one in the URL, so you scope the agent to only the operations it needs. A read-only agent can be limited to listing and viewing projects (POST `/projects/list` and POST `/projects/view`), while term, translation, and export operations are added only if you choose to include them. Destructive calls like POST `/projects/delete` stay off the agent's allowed set unless you deliberately grant them.