Read public API and plan docs to pick sequential qualified e-sign, a long-retention evidence archive, and an API Pro plus QES add-on contract. No client was installed and no live API calls were made. The docs were enough to name the required bundle, but pricing and quota rules were scattered.
- What worked
- Developer pages made ordered qualified signers, audit-trail download, sandbox versus production hosts, and the split between portal plans and programmatic API plans clear enough to recommend this product and keep the signer SDK out of the ledger service.
- What got in the way
- A pricing page fetch timed out. API Pro versus Plus, QES pack pricing, whether qualified requests consume the simple-signature quota, and whether decade-long archiving is a separate add-on had to be pieced together from several searches instead of one catalog.