How do you translate comic chapters through an API?
A publisher with 40 series does not want a person to drag folders into a web app. Here is the whole loop in five requests.
With the Bublate API, a publisher creates a chapter, uploads its pages with one PUT per image, and starts it in one or more target languages. Bublate reads the text, translates it with a series bible, erases the old lettering and letters the new text. A signed webhook calls your server when the chapter is ready, and each lettered page has a download link.
Studios and publishers keep their pages in their own systems: a content management system, a shared drive, an asset server. The Bublate API lets those systems send a chapter in and get the lettered pages back, without anyone opening the app. This post walks through the five requests and the webhook, with the rules that keep it safe to automate.
What does a request need?
One header. The workspace owner creates a key in the app (account menu, API and webhooks), and every request sends it as a bearer token. A key acts as the owner of its workspace and spends that workspace's credits at the same price as the app. Bublate stores only a SHA-256 hash of the key, so the key is shown once.
Authorization: Bearer bub_...Which requests translate a chapter?
Five, in this order. The base URL is https://bublate.com/api/v1.
# 1. Create the chapter (in a new series, or pass seriesId)
curl https://bublate.com/api/v1/chapters -H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" \
-d '{"seriesTitle": "Moonlit Garden", "number": "12", "srcLang": "Korean", "format": "webtoon"}'
# 2. Upload each page (PNG, JPG or WebP, 30 MB at most, read in file name order)
curl -X PUT https://bublate.com/api/v1/chapters/$CHAPTER/pages/0001.jpg \
-H "Authorization: Bearer $KEY" -H "Content-Type: image/jpeg" --data-binary @0001.jpg
# 3. Check the price
curl https://bublate.com/api/v1/chapters/$CHAPTER/quote -H "Authorization: Bearer $KEY"
# 4. Start, with the rights confirmed
curl https://bublate.com/api/v1/chapters/$CHAPTER/start -H "Authorization: Bearer $KEY" \
-H "Content-Type: application/json" -d '{"targets": ["English", "Spanish"], "rights": true}'
# 5. Read the status and the files of one language
curl https://bublate.com/api/v1/versions/$VERSION -H "Authorization: Bearer $KEY"Each target language becomes a version with its own id and status: queued, translating, review (ready), done, exported or failed. A failed version gives its credits back. When a version reaches review, its files list holds the lettered segments in reading order. Each file has a url that needs the key and a download link that works without it for one hour, for a browser or a script that cannot send headers.
How is the price set?
From the pages themselves, before anything runs. A webtoon chapter of up to 20 segments costs 10 credits per language ($3), and each further 10 segments add 5 credits. Print pages, such as manga, cost at most 2 credits a page. GET /chapters/{id}/quote answers the exact price of an uploaded chapter and the credits the workspace can spend. POST /quote with page sizes in pixels gives an estimate before the upload. If the workspace has too few credits, the start answers 402 and charges nothing. What a chapter costs shows where the money goes.
Why must the caller confirm the rights?
Because a script cannot see whose comic it sends. POST /start refuses to run without rights: true, and Bublate records which person confirmed the rights and when. The Acceptable Use Policy applies to API calls as it does to the app. We kept this as a required field rather than a terms checkbox at sign-up, so the confirmation sits next to each chapter.
How does Bublate tell your server that a chapter is ready?
With a webhook. Add an https endpoint in the app, or with the key (POST /webhooks, which tools such as Zapier and n8n use to subscribe). Bublate sends a POST when a version changes state: version.review, version.failed, version.done or version.exported. Each delivery carries x-bublate-signature: t=<unix time>,v1=<hex>, where v1 is the HMAC-SHA256 of t.body with the endpoint's signing secret.
import crypto from 'node:crypto'
function verify(rawBody, header, secret) {
const { t, v1 } = Object.fromEntries(header.split(',').map((p) => p.split('=')))
const mac = crypto.createHmac('sha256', secret).update(`${t}.${rawBody}`).digest('hex')
const fresh = Math.abs(Date.now() / 1000 - Number(t)) < 300
return fresh && crypto.timingSafeEqual(Buffer.from(mac), Buffer.from(v1))
}Two rules protect both sides. Bublate resolves the endpoint's host before every delivery and refuses private, loopback and reserved addresses, so a webhook cannot be aimed at an internal network. And an endpoint that fails 20 deliveries in a row turns itself off until the owner turns it on again.
What are the limits?
- 1,000 pages a chapter and 30 MB a page.
- 20 keys and 10 webhook endpoints per workspace.
- Up to 20 chapters translate at the same time across all workspaces. More wait in a queue and start in order.
- A chapter takes about 10 minutes per language.
The full reference, with every field, is on the developers page. The same API also powers the Bublate MCP server, which lets an assistant such as Claude run these steps for you.
Frequently asked questions
Is there an API for webtoon and manga translation?
Yes. The Bublate API at bublate.com/api/v1 creates a chapter, takes its pages, starts translation and lettering in one or more languages, and returns the lettered pages. A key from the app signs each request.
How much does the comic translation API cost?
The same as the app: 10 credits ($3) per language for a webtoon chapter of up to 20 segments, 5 more credits for each further 10 segments, and at most 2 credits a page for print pages such as manga. New accounts get 30 free credits once.
How do I know when a chapter is ready?
Poll GET /versions/{id} until the status is review, or add a webhook. Bublate sends a signed POST with the event version.review when a translation is ready, and version.failed when it fails and its credits come back.
Can I download the pages without the API key?
Yes, for one hour. Each file in a finished version has a download link signed with an expiry time, for browsers and tools that cannot send an Authorization header.
Sources
- Bublate API reference · checked
- Bublate Acceptable Use Policy · checked
- RFC 2104, HMAC: Keyed-Hashing for Message Authentication · checked
Related
Written by the Bublate team. We build tools that translate and letter comics, and we publish what we measure along the way.
Stories about comics in every language, once a month
Related articles
Translate a comic chapter from Claude or ChatGPT (MCP)
By the Bublate teamBublate runs a remote MCP server at bublate.com/mcp. Connect Claude, ChatGPT or Cursor, and ask it to translate and re-letter a webtoon or manga chapter.
What a chapter costs: manga translation rates in 2026
By the Bublate teamManga translation rates by role, per page and per chapter: translator, letterer, sound effects and proofreader, with sources, next to the cost of software.