Generate client SDKs straight from an API document
SDK generators are great — when you have a spec. The hard part with legacy vendors is that there is no spec: just a PDF or Word reference. The usual path is hand-writing OpenAPI first, then running a generator, which means the slowest step is still manual.
pdf2api collapses that pipeline: upload the document, get an extracted OpenAPI 3.1 spec, and download Java, PHP and TypeScript SDK drafts generated from it — one payment, all three languages.
What you get per language
Each SDK is generated with openapi-generator from the extracted spec, packaged as a zip:
- •Typed request/response models matching the document's parameter tables
- •A client class per resource group with one method per endpoint
- •Auth plumbing for detected schemes (API keys, bearer tokens)
- •Standard project scaffolding — build files, package metadata — ready to vendor into your repo
Drafts, honestly labeled
Where the source document requires things code generation cannot infer — request signing, body encryption, vendor token exchanges — the spec carries explicit warnings, and those land in the SDK docs too. You implement those few pieces by hand; the other 90% of the boilerplate is already written.
If you only need the spec or the Postman collection, the same payment covers those exports as well.
Frequently asked questions
Which languages are available?
Java, PHP and TypeScript today. The OpenAPI 3.1 export means you can run any other openapi-generator target yourself for free.
Are the SDKs production-ready?
They are engineered drafts: compile-ready scaffolding generated from the extracted spec. Review them like you would a teammate's first PR — especially around flagged warnings.
Can I regenerate after fixing the spec?
Yes — download the OpenAPI file, edit it, and run openapi-generator locally with any settings you like. The export is yours.
Skip the hand-written spec step
Document in, three SDK drafts out. Preview free.
Upload your API doc →