Documateo

API · In development

Programmatic access, on the way.

A REST API for the same processing engines behind documateo.com — 97 tools you can call from your own app or pipeline. Currently in development for Business plans.

What's planned

Designed for pipelines, not just one-off calls

API-key authentication

Keys are separate from account sessions, so you can rotate or revoke them without touching anyone's login.

Every tool, one request

The same engines behind the website — merge, compress, convert, OCR and more — callable directly from your own app or pipeline.

Async jobs for heavy work

Video and Office conversion run as jobs, with webhook or polling-based status so your code never has to hold a connection open.

Usage on the same credits

Calls are billed against the same credit system as Business plan passes — no separate meter to reconcile.

Planned design — details may change before launch.

How a call will work

The same job model the web app already runs on

  1. 01

    Submit

    Send the file and the tool you want. The request is validated and a job is created.

  2. 02

    Track

    Poll the job or receive a webhook as it moves from queued to processing.

  3. 03

    Collect

    Download the result when the job is done. If it fails on our side, the credits are returned.

  4. 04

    Expire

    Inputs and outputs expire automatically — on the web app today, nothing outlives the retention window in our Privacy Policy.

Ideas

What teams could build with it

  • Compress or resize user uploads before you store them
  • Convert Word, Excel or PowerPoint files to PDF inside a workflow
  • Make scanned PDFs searchable with OCR as part of document intake
  • Generate invoices and receipts from the data you already have

Use it today

Every tool already works in the browser

Until the API ships, all 97 tools are available on the website — 61 of them with no signup and no upload.

Browse all tools →

API questions

When will the API launch?
There's no date yet. We would rather ship it properly than announce a deadline. Early-access requests help us decide what to build first.
Who will get access?
The API is being built for Business plan accounts. Tell us what you'd build and we'll come back to you as it takes shape.
Will you keep my files?
The plan is to follow the same rules as the web app: automatic expiry of inputs and outputs, and no use of your files to train models.

Tell us what you'd build

A few lines about your use case is all we need. Early requests shape what ships first.