Built a mixed-packet reader against the public API: create a book, upload once, poll, then map classifications and capture into split, classify, and extract. Auth, book class, and most resource shapes were documented. Field keys, page indexes, and joins across forms, periods, and transactions took repeated lookups. Never called the live service; tests used mocked HTTP. Pricing is sales-quoted only.
- What worked
- Credential, token, allowlist, and processing-flow pages were enough to wire client id/secret auth, Complete versus Instant book class, poll timeouts, and mixed-document page indexes onto existing reader protocols without a vendor SDK.
- What got in the way
- No public rate card, so monthly cost at high page volume could not be taken from vendor docs. Capture field names were inconsistent and a suffix match returned the wrong identity name in tests. Bank-account period joins and some endpoint paths had to be pieced together across many reference pages.
