Pditor API

What it looks like

Send a tool name + base64-encoded file input(s) + tool-specific params with an X-Pditor-Key header. Get back a job ID with a poll URL. The 33 tools you can call are the same ones running the web UI — no parallel surface to maintain.

curl -X POST https://api.pditor.com/api/v1/jobs \
  -H "X-Pditor-Key: pdr_..." \
  -H "content-type: application/json" \
  -d '{
    "tool": "compress",
    "params": { "level": "medium" },
    "inputs": [
      { "filename": "doc.pdf",
        "data": "JVBERi0xLjcKJeLjz9MK..." }
    ]
  }'

# Response (HTTP 202):
# { "job_id": "...", "status": "queued",
#   "credits_charged": 1, "credits_remaining": 499,
#   "poll_url": "/api/v1/jobs/<id>" }

Full machine-readable schema at /api/v1/openapi.json (OpenAPI 3). Hand-written for now; SDK packages (Python, Node, Go) ship with the public beta.

Pricing

Credit-based, charged per call. Transform tools (compress, rotate, merge, etc.) are 1 credit each; AI tools (summarize, translate, compare, chat) are 2 credits. Closed-beta participants start with 500 credits free. Public-beta pricing publishes ahead of the retail launch.

Closed beta — join the waitlist

We're inviting 100 developers in batches starting Month 6. Email support@pditor.com (with "API waitlist" in the subject) with a one-line description of what you'd build and we'll add you to the queue. We pull invites in submission order.

Why a closed beta?

The compute side is the same engine that drives the web; we don't need to scale that. The closed beta is about iterating on the SDK surface, the error model, and the credit-meter UX before we commit to long-term backwards compatibility.