What Clicksign API is
Clicksign API gives developers tools for building electronic-signature workflows with envelopes. The Envelope API can create envelopes, attach documents, add signers, define authentication requirements, and activate signing flows. Requests and responses use JSON:API formatting. Webhooks send HTTP POST notifications to a registered URL when signature events occur, while an embedded widget places signing inside a website or application. The API includes identity verification, workflow status access, and signed-file retrieval. Clicksign offers an unlimited free sandbox for trying integrations before launch, and billing is based on documents finalized by all signers rather than documents merely sent. API access is available on every plan, though the maker says integrations generally require development and technical support. Connection options include API, Zapier, Salesforce, and TOTVS. Clicksign states that its signatures comply with Brazilian legal requirements and lists ISO 27001 and ISO 27701 certifications.
Who it suits
Clicksign API suits developers and organizations building customized signing flows into websites, applications, or business systems. It is aimed at more complex integrations that have development resources.
Good to know, and what to watch
- Envelope API manages documents, signers, and authentication
- JSON:API requests and responses
- Webhooks report signature events
- Unlimited free sandbox
- Embedded signing widget
- No free plan
- Integrations generally require development work
- Advanced plan starts at 300 documents monthly
Plans
Every plan and priceAvançado
Start
Plus
Automação
The verdict
Clicksign API provides the core building blocks for embedded, automated electronic signatures. Its sandbox, webhooks, and status APIs support integration work, while development requirements make it less suited to purely nontechnical use.
What the maker publishes
- API availability
- The integrations FAQ says API access is available on all plans, while API integrations generally require development and technical support. source
- API format
- The Envelope API uses JSON:API formatting for requests and responses. source
- Billing basis
- The integration page says customers pay for documents finalized by all signers, rather than documents merely sent. source
- Embedded signing
- The integration page says the embedded widget can place the signature flow directly inside a website or application. source
- Founded
- 2010 source
- Free plan
- No source
- Hosting and encryption
- The homepage states that Clicksign uses AWS Multi-AZ infrastructure, TLS 1.3 in transit, and AES-256 at rest. source
- Integrations
- The maker lists API, Zapier, Salesforce, and TOTVS as ways to connect Clicksign with business systems. source
- Intended users
- The maker describes API integrations as suited to more complex scenarios and says they generally require development. source
- Legal framework
- The maker says its electronic signatures comply with Brazilian Provisional Measure 2.200-2/2001 and Law 14.063/2020. source
- Purpose
- The Envelope API lets developers create envelopes, add documents and signers, set signer authentication requirements, and activate signature flows. source
- Sandbox
- The integration page describes an unlimited, free sandbox for testing integrations before launch. source
- Security certifications
- Clicksign says it holds ISO 27001 and ISO 27701 certifications for information security and privacy. source
- Security practices
- The security page describes least-privilege access controls, periodic vulnerability testing and risk assessments, backups, and annual independent audits. source
- Support
- The API documentation links users to Clicksign support, and the pricing page lists priority support for the Advanced plan. source
- Webhooks
- Webhooks send HTTP POST notifications to a registered URL when a signature event occurs. source
Checked against the maker's pages on 3 Oct 2026.