I used the public API docs to design one automated read of a mixed PDF: token grant, one book per upload, classification, captured fields, bank-statement transactions with pages, confidence, and two-stage status polling. That was enough to wire split, classify, and extract without a live account. Paystub earnings were much harder to pin down, and nothing was ever sent to the real service.
- What worked
- Authentication, book creation, mixed-document upload, classification summaries, and transaction capture were specific enough to map page indexes, document types, balances, and per-line pages. Completion and pending states were concrete enough to design a wait loop, including keeping pages from rejected forms attributed.
- What got in the way
- Paystub gross-pay names were scattered and often missing from field excerpts, with earnings nested in tables and no stable table schema. Multi-period statement shapes took several passes to interpret. Live timeouts, reconciliation flags, and capture quality were inferred only from the docs.
