A document pipeline you do not have to operate.

PDF tooling, conversion binaries, upload handling, and output storage end up running on a web server that was never meant for them.

Start building Read the docs

PDF received

test

quarterly-report.pdf

PDF · 18 pages · 4.2 MB

Accepted

Stored before any processing starts. Job job_parse_7ab2 was returned with HTTP 202.

Result

Waiting for the worker. Poll GET /v1/file-jobs/{id} until it finishes.

job: job_parse_7ab2
attempt: —

How Flowyn handles it

What you get instead of building it.

Upload once

Files are stored and given an id before any operation runs.

Operations as jobs

Parse, convert, and split are asynchronous jobs with attempts and status.

Structured outputs

Markdown, JSON, text, or PDF outputs linked to the source file.

Honest results

Pages without a text layer are returned empty. No OCR is performed.

API example

A real request against the Flowyn REST API.

Full request and response contracts are in the docs.

Limits worth knowing

No OCR; text-layer PDFs only
Files up to 50 MB and 200 pages
Processing is asynchronous (HTTP 202)

POSThttps://api.flowyn.dev/v1/pdf/parse202

curl -X POST https://api.flowyn.dev/v1/pdf/parse \
  -H "Authorization: Bearer flw_test_••••" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: parse-quarterly-001" \
  -d '{
    "file_id": "9c1e5b7a-2d4f-4a6b-8e3c-1f0a7d2b5c64",
    "output": "markdown"
  }'