Skip to main content

Get started with the SignNow API

Embed eSignatures and workflows using the SignNow REST API.

The SignNow REST API lets your website or app send, sign, and track documents automatically. Embed signing, prefill templates, route by role, and get real-time status via webhooks—secure, compliant, and built for scale. Trigger sends, route templates by role, and track progress via webhooks—all with audit-ready security. Common uses include auto-sending NDAs from your CRM when an opportunity opens, generating onboarding packets from your HRIS on “new hire,” collecting customer agreements inside a web/mobile app, and streamlining vendor onboarding from your procurement system. You can also build self-serve flows with invite links, enforce authentication, and store signed PDFs and certificates back to your cloud drive or DMS.

What is an API?

An API is a way for your software to “click the buttons” in SignNow—without a human. The SignNow REST API exposes core features (sending invites, filling templates, embedded signing, downloading signed PDFs + Audit Trail) so you can run e-signature workflows from your own app, CRM, portal, or cloud system.

What you can build

  • CRM → NDA: When an opportunity reaches “Discovery,” create an NDA from a template, prefill the company name, and email invites automatically.

  • HRIS → Onboarding pack: On “employee created,” generate an offer + policies bundle with roles (Employee → Manager → HR) and enforce the signing order.

  • In-app contracts: Embed the signer view so customers complete agreements without leaving your site/app.

  • Vendor onboarding: Collect W-9s and certificates with Attachment fields (Enterprise), store everything back to your DMS, and tag for search.

How SignNow concepts map to the API

  • Templates & roles: Define fields and recipients once; the API creates documents from them.

  • Signing order: Enforce sequential or parallel steps programmatically.

  • Pre-filled Text & Labels: Prefill values you know; keep repeated answers in sync.

  • Authentication: Add passcode/SMS/email OTP for stronger identity checks.

  • Audit Trail (Document History): Download signed PDFs with the certificate of events.

📝 API is not a part of a regular self-serve subscription package. Click here to learn more about the API pricing.

Check out our documentation page here.

What’s next

  • Set up a sandbox, create a template with roles, and try a small end-to-end flow (create → send → sign → download with History).

  • When it looks good, move credentials to production and enable webhooks for live tracking.

Did this answer your question?