Read licensing and overview docs to pick a native signing path that keeps files in an existing library. Designed sequential send, completion dates, and activation around that service, but never called it live. There is no public create-request API, so the app records recipients and depends on a workflow or a manual send in the library.
- What worked
- Docs were clear that a finished copy can return to the same library, that staff can sign with existing work accounts, and that billing is pay-as-you-go instead of a new vendor.
- What got in the way
- External signers appear to need directory guest objects, which conflicted with email-only counterparties. No documented API starts a request, so the application could not send signing from code and the live service was never exercised.