Developers

PDF to Word API

Same HTML → Word pipeline as the studio, for other products. Authenticate with Authorization: Bearer pdt_live_… (issued in Admin). Credits hold a per-page ceiling, then settle to measured usage. 402 means the wallet is short; 429 is quota.

What you get

A reconstructed HTML page you can store or display, and a Word file generated from that HTML — not a separate flattened conversion. Use it when a product needs layout-faithful DOCX for letters, illustrated spreads, or ID cards. The human workflow is on how it works.

Call sequence

1. POST /v1/uploads/init — signed upload URL
2. PUT the file bytes to that URL
3. POST /v1/jobs — start conversion (document_type: auto | letter | layout | id)
4. Poll GET /v1/jobs/{id} until done
5. GET /v1/jobs/{id}/docx — Word built from the reconstructed HTML

document_type

• auto — classify on the server (same as the web upload).
• letter — running text, correspondence, reports.
• layout — jackets, illustrated spreads, artwork pages.
• id — card-shaped scans with photo and fields.

Try-it-out below talks to this origin (/v1 is proxied). Paste your key in Authorize. Partner access is invite-only — contact us for a key, or sign in to use the web converter. Prepaid credits are on pricing.

Questions

How do I authenticate?

Send Authorization: Bearer pdt_live_… on every /v1 call. Keys are issued in Admin, shown once, and stored as hashes.

What does document_type mean?

auto, letter, layout, or id. auto classifies the upload. letter is running text, layout is illustrated spreads and jackets, id is card-shaped scans.

What is 402 vs 429?

402 means the wallet cannot cover the hold. 429 is quota. Credits hold a per-page ceiling, then settle to measured usage.

Is the Word file built from HTML?

Yes. GET /v1/jobs/{id}/docx returns Word generated from the reconstructed HTML — the same pipeline as the studio.