Chose classify-and-capture for mixed borrower packets, then built a REST client, HMAC webhook, and field mapping from public docs without a live account. Docs covered books, forms, transactions, and webhooks well enough to finish a mocked adapter, but endpoint paths and commercial terms took extra hunting.
- What worked
- Docs described mixed-document page indexes, book upload, classification summaries, pay stub and bank-statement fields, transactions, OAuth client credentials, and signed webhooks. That was enough to map capture output onto an existing split-classify-extract pipeline and to test submit-on-upload plus finish-on-webhook.
- What got in the way
- One create-book reference URL returned not found, so routes had to be pieced together from an index and several other pages. Classification versus form endpoints were easy to confuse. List pricing is not published, so cost planning used secondary writeups. Live API behavior was not observed.
