Parsli documentation

Start here

Parsli documentation

Turn any document into structured data. Start with the five-minute walkthrough, or jump straight to the API.


Parsli reads documents — invoices, receipts, statements, forms, scans, photos, handwriting — and gives you back clean, structured data you can actually use.

These docs are written for two people at once: someone setting Parsli up without writing any code, and someone wiring it into their own system. Pages stay in plain English. Where a word has a precise technical meaning, it links to the Dictionary, so you get the detail only if you want it.

Start where you are

Never used Parsli. Read what Parsli does, then follow your first extraction. About five minutes, and you will have real data out of a real document.

Setting it up for your team. Do the walkthrough first, then how Parsli works so the pieces make sense before you build something everyone depends on.

Writing code against it. The object model is in how Parsli works and the Dictionary — both are short. Every term carries the payload keys and types alongside the plain description.

Working out what it costs. How pages are counted explains the unit. Free pages and plans covers what you get for nothing and what happens after.

The one idea worth knowing up front

Everything in Parsli hangs off a Parser. A parser is a reusable setup for one kind of document — you might have one for supplier invoices and another for bank statements. You tell it what to pull out once, and then every document you send it comes back the same shape.

That is the whole model. Documents go in, structured data comes out, and a parser is the thing in the middle that knows what you wanted.

Reading these docs as a machine

If you are an AI agent or you are building one, there are cheaper ways to read this than parsing HTML:

  • Add .md to any docs URL for the raw markdown — /docs/start-here/how-parsli-works.md
  • Request any docs page with Accept: text/markdown for the same thing
  • /llms.txt is a compact index of every page
  • /llms-full.txt is the entire documentation in one file
  • /docs/dictionary.json is the full object model as structured data — the fastest way to learn the vocabulary in one request

Something here wrong or missing? Tell us — we treat it as a bug.