APIDevelopers

A simple PDF and image API for developers: merge, compress and stamp from code

Add PDF merging, page numbers, watermarks, image compression and verification stamps to your app with one HTTP request. Examples in curl, JavaScript and Python.

· 6 min read

Building PDF handling into an app usually means picking a library, handling edge cases like encrypted or corrupted files, and running image processing on your own servers. The DocuTools API gives you the same tools as the website through simple HTTP requests, billed in the same credits.

Getting started

  1. Create an account and verify your email.
  2. Go to Settings → API keys and create a key. It is shown once, so store it safely.
  3. Send requests with the header Authorization: Bearer dt_your_key.

What you can call

  • POST /api/v1/tools/{slug}: run one tool. Send files as multipart form data in the "files" field, options as text fields. The response body is the result file.
  • POST /api/v1/workflow: run 2 to 6 tools in a row in one request.
  • GET /api/v1/credits: daily and purchased credits left, and the next reset time.
  • GET /api/v1/tools: the list of tools, their cost and options.
  • GET /api/v1/status: service health, no key needed.

Example: merge two PDFs and stamp the result

One workflow request merges the files and adds a verification stamp. The response includes an X-Stamp-Code header you can store with the document, so your users can verify it later at /verify.

See every endpoint with examplesAPI documentation

Credits, limits and errors

  • API jobs use the same credits as the website: daily plan credits first, then purchased credits.
  • Failed jobs are free. Errors return JSON with a clear message and a standard HTTP status code.
  • Each account can run up to 100 jobs per hour across web and API.
  • Files are processed in memory and never stored.

Check GET /api/v1/status from your monitoring to know right away if the service is degraded.