Developer API

Document Translation API for PDF, Word, Excel, and PowerPoint

Use one asynchronous API for PDF, Word, Excel, and PowerPoint translation. Keep your integration simple: submit a file, poll status, then download the translated result.

Open Developer Center View pricing

POST/openapi/v1/pdf/tasks

POST/openapi/v1/office/tasks

GET/openapi/v1/tasks/{id}

GET/openapi/v1/tasks/{id}/download

Workflow

A predictable asynchronous workflow

The API returns quickly after a task is accepted. Your service stays in control while translation continues in the background.

Authenticate

Create an API key in the Developer Center. Keys are shown only once and can be revoked at any time.

Submit a document

Send a PDF or Office file with a target language and an Idempotency-Key to protect retries.

Poll and download

Check the task until it succeeds, then download the translated file from the result URL.

Capabilities

Built for document workflows

PDF translation

Submit native or scanned PDFs and retrieve a translated PDF when processing finishes.

Office translation

Translate DOCX, PPTX, and XLSX files while keeping the result ready for continued editing.

Shared credits

The API and web workspace use one credits balance, so teams can combine manual and automated workflows.

Credits

Clear page-based billing

PDF and Office translation are charged at 1,500 credits per billable page. PDF uses physical pages; PPTX uses slides; DOCX uses embedded page count with a one-page fallback; XLSX uses worksheets.

MCP integration

Bring document translation into your AI workspace

Connect one API key once in Codex, Claude, Cursor, Trae, or another client that supports remote MCP. Your AI workspace can check credits, create translation tasks, poll progress, and download the result without leaving its normal flow.

Remote MCPhttps://www.fanyipaiban.com/translate/mcp

Codex

Codex: add the remote server URL and point bearer_token_env_var to FYPB_API_KEY in ~/.codex/config.toml.

Claude / Cursor / Trae

Claude, Cursor, and Trae: add an HTTP MCP server in settings with the URL and Authorization: Bearer <API_KEY> header.

The same page-based credits price applies. PDF, DOCX, PPTX, and XLSX are supported. For a local file above 20 MB, use the REST API upload flow.

Start with the integration guide

The Developer Center includes request examples, authentication rules, idempotency guidance, task responses, download flow, and call records.

Open API documentation