Docpier Partner APIs are server-to-server HTTP contracts. One OAuth client, Swiss hosting, asynchronous jobs. You send the document; we notify you when data or a booking is ready.
Partners embed Docpier behind their own UX — ERP, DMS, banking, or a fiduciary portal. End users never talk to Keycloak. Your backend obtains a client-credentials token, writes a job (202), acknowledges a webhook, then GETs the result. Polling is not the integration model.
Two products are live today: Docmind (extract structured data for your own screens) and Docbooks (book the document). Docbooks uses Docpier extraction behind the scenes — you POST the file to Docbooks, not to Docmind first. Call both APIs only if you need capture as a separate capability. Workspace ids are not shared; you store the mapping.
Turn a PDF or image into typed business data: invoices, receipts, statements, and the rest of the released document types. Your system of record keeps the file; Docmind returns structured JSON after processing finishes.
Submit a receipt to a Docbooks workspace and receive a booking job. Extraction is used behind the scenes; the partner contract is the booking, not a Docmind document id.
A dedicated HTTP API to split multi-document PDFs into logical files before capture or booking. Today, split is an option on Docmind extract and on Docbooks booking metadata.
Create and fetch partners, organisations, workspaces, and product settings. It will take over onboarding and offboarding that Docbooks exposes today.
Route extracted invoices through review, approval, posting, and payment. Built on capture; exposed as its own partner API later.