Toolty API reference

The API is REST over HTTPS, with JSON bodies. Files never go through the API itself: you upload to, and download from, short-lived signed URLs. A job goes through four calls: open, upload, start, fetch the result.

Base URL

https://toolty.io/api/v1/public

Send your key in the Authorization header. Create keys in your account, under API: a key is shown once, only its fingerprint is kept, and you can revoke it at any time.

Authorization: Bearer tk_live_…

Errors return an HTTP status and a JSON body with an error code.

60 calls per minute per key, two jobs running at once. Uploaded files and results are deleted at most one hour after processing.

Pass a webhook HTTPS URL when you start a job. When it ends, we POST the job to it, signed with your key's webhook secret (shown in your account). We retry after 1 min, 5 min, 30 min, 2 h, 6 h, 12 h and 24 h until we get a 2xx answer. With Zapier, Make or n8n, use their generic HTTP modules and a “Catch hook” trigger.

{
  "id": "1d7e…",
  "type": "job.completed",
  "createdAt": "2026-11-05T14:42:10.000Z",
  "data": {
    "job": { "id": "6f1c…", "tool": "word-to-pdf", "status": "succeeded", "result": { "size": 51022, "expiresAt": "2026-11-05T15:42:00.000Z" } }
  }
}

import crypto from "node:crypto"

// header = req.headers["toolty-signature"]  →  "t=1762351200,v1=5f2c…"
function verify(header, rawBody, secret) {
  const { t, v1 } = Object.fromEntries(header.split(",").map((p) => p.split("=")))
  const expected = 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(v1), Buffer.from(expected))
}

Every tool the API will cover. Each delivered result is billed per second of processing, from the moment a worker starts the job to its end, rounded up to the next second, at the tool's price per second. Failed jobs are not billed. Opening or starting a job requires a balance covering one minute of the tool's processing. A tool marked Soon is documented but not callable yet, and a job opened with it is refused with tool_not_available.