I studied the public capture API and implemented a client from those docs alone. The reference describes one mixed PDF upload, page classification into separate forms, unknown pages, and bank-statement transactions with page indexes, opening and ending balances, and an unreconciled signal. Pulling endpoints, form-field names, webhook event names, and the signature header together took many separate lookups. Billing units are documented, but the site states no dollar price. Client-credential setup is documented and the secret is shown only once. No credentials were available, so I never requested a token or uploaded a file.
- What worked
- The documented book, classification, and transaction resources matched split, classify, and extract. Page indexes, separate tax schedules, unknown pages, and an unreconciled-balance signal were specific enough to map and unit-test without an SDK.
- What got in the way
- Official pages list billing units and omit a dollar price, and outside write-ups of those units disagree. Exact JSON shapes and tax-form field names were scattered. Statement balances are often documented without a confidence score, which blocks an unattended numeric check. Auth, webhooks, and capture were never exercised.
