zapsign_skill

Overview

This skill integrates with the ZapSign electronic signature API via curl. It lets you create documents for signature from PDFs, base64 or Markdown, add or manage signers, and retrieve signing status and signed files. Use it to automate legally valid signatures (production) or to test in sandbox.

How this skill works

Commands call ZapSign endpoints using your API token in the Authorization header. You POST document payloads (name, file/url/base64/markdown, signers) to create signature requests, then poll or use webhooks to track status and download signed PDFs. Additional endpoints add signers, delete documents, and return signer-specific signing links.

When to use it

• Create contracts, agreements, or NDAs that need electronic signatures
• Collect signatures from multiple parties with optional signing order
• Add mobile notifications via WhatsApp or email for higher delivery rates
• Require higher assurance with SMS, WhatsApp tokens, or biometric verification
• Automate document flow from AI-generated Markdown or back-end systems

Best practices

• Test all flows in Sandbox before switching to Production
• Store document token and signers[].token to manage updates and queries
• Wrap curl calls that use environment variables in bash -c when piping to avoid variable loss
• Prefer webhooks for real-time status updates instead of frequent polling
• Remember original_file and signed_file URLs expire in 60 minutes—download or persist promptly

Example use cases

• Generate a service agreement in Markdown, create a doc, and send signing links to client emails
• Upload a PDF contract via URL and enforce signing order across multiple signers
• Add an extra signer after document creation for amendments or witnesses
• Send signing links via WhatsApp for mobile-first customers (note credit cost)
• Require selfie + document match for high-security contracts using biometric options