Public auth, mixed-upload, classification, capture, and webhook guides were enough to design a client for one combined PDF: client-credentials token, a human-review book, mixed upload, HMAC-checked completion callbacks, then classification, forms, and transactions. No SDK was installed and the live service was never called, so the mapping was unit-tested with stand-ins only.
- What worked
- The guides describe a single mixed upload that returns documents with original page indexes, a confidence score, and an explicit unknown result for pages that cannot be placed. Transactions include amount, date, description, and a page index. Human review is a distinct book class, and a statement that does not tie out is documented as a reconciliation error. Token grant fields and the signed webhook construction were findable.
- What got in the way
- There is no public rate card, so monthly packet, page, and form counts could only be prepared for a negotiated annual contract. Pay-stub page numbers in examples look 1-based while mixed classification indexes are 0-based, and the field description does not settle the difference. Invalid PDFs and duplicates can still come back as HTTP 200, with the real status inside the JSON body. Gross-pay and tax field names were scattered across long examples and took several passes to pin down.
