DevConvert API
83 tools are available as a JSON/binary REST API under /api/*, for scripts and Postman/curl -- not just the browser forms. The spec below (/api/openapi.json) is generated straight from the same route registrations, so it can't drift from what's actually live.
Calling conventions
- Every endpoint is
POST /api/<tool-slug>(the same slug as its web page's URL). - Text/JSON-in tools accept either a JSON body (
Content-Type: application/json) or a regular form-encoded body -- same field names either way. - File-in tools take
multipart/form-data-- see each endpoint's field names below (usuallyfile,files, orfile_a/file_b). - A tool that produces a document/image/archive on the web page returns that same binary content directly (correct
Content-Type), not a base64 JSON blob. - A tool that shows text/structured output on the web page returns
{"result": ..., "warnings": [...]}as JSON. - Invalid input always comes back as HTTP 400 with
{"error": "..."}-- the same messages the web forms show. - Project/directory-shaped tools (Terraform↔CDK, HTML→React/Angular/Ionic) and the two inherently interactive ones (PDF Form Filler, PDF Editor) are web-only -- they don't reduce to one request/response call.