Define the customer journey first
Write down what starts a packet: a customer completing onboarding, a staff member approving a job or another action in your own system. Identify which fields come from your application and which the signer needs to complete.
Decide whether recipients will follow an invitation link or complete signing inside your site. For embedded signing, configure and test the permitted embedding domains and follow the current account documentation. API availability does not imply every integration pattern is included on every plan.
Keep credentials and private links protected
Use the documented authentication mechanism from your server. Do not put private API credentials in browser code, public repositories or analytics events. Treat signing links as private and avoid including document contents in routine logs.
Use the documented request formats and status behavior. If a request times out, check whether the intended operation already succeeded before retrying it. Test duplicate delivery, failed sends and expired links with non-customer data.
Build around actual credit and signer states
Every packet uses one credit, regardless of file or page count. Upload limits are 20 MB per file and 100 MB per packet. The interactive sending flow displays exact credit usage before sending; for an integration, verify the documented validation and credit requirements for the operation you use.
Sending holds credits and at least one signer completing signing consumes them. Full packet completion is a separate state. If nobody completes signing and the packet is voided or expires, its credit hold is released subject to original expiry. Do not send a “completed PDF ready” message merely because one signer finished.
Test before connecting customer traffic
Use fictional records for the integration rehearsal.
- Confirm API and embedding are enabled in the selected plan.
- Check the current account documentation for endpoints and authentication.
- Exercise a normal request, a validation failure and a safe retry.
- Test one signer completing while another remains pending.
- Test full completion, an unsigned expiration and the corresponding credit state.
- Check the actual signer view on desktop and mobile.