What IgniSign is not
So that you do not spend a week integrating the wrong tool.
IgniSign is an API that developers add to their own product to collect simple and advanced electronic signatures and keep the proof. It is not a qualified trust service provider, it does not issue qualified signatures or connect to national eID schemes, it is not a contract-lifecycle, document-management or board-governance tool, and it is not a web console for uploading and sending PDFs without integration.
You need a qualified electronic signature (QES)
Not offered. IgniSign provides simple and advanced electronic signatures only. If your flow legally requires a qualified electronic signature, IgniSign is not the right tool.
Signature levels
You need a national eID scheme to identify signers
IgniSign has no eID connector. Identity verification uses an automated ID document and selfie check, open banking or SSN verification.
Identity-check signatures
You want to upload a PDF and send it for signature, without integration
The console exists for testing and operations, but IgniSign is priced and built for API use: the value is the signature step inside your own product. If you have a product, start with the API.
Start with the API
You want a no-code only workflow (Zapier, Make, n8n, HubSpot)
Connectors exist and are documented for developers who already use these platforms. They are not the product and are not offered as a stand-alone service.
Connectors documentation
You need contract lifecycle management, templates, negotiation or document management
Not in scope. IgniSign signs what your application prepares and returns the proof; the workflow around it is yours.
Start with the API
You need a board portal, meeting minutes or governance workflows
Not in scope. IgniSign is a signature API, not a governance tool.
You need long-term archiving, long-term validation or qualified timestamps
Not offered. IgniSign does not provide long-term validation and never describes its timestamps as qualified. You retrieve and keep the proof files yourself.
Signature proofs
You expect signer reminders or automatic webhook retries
Not implemented. Use the webhook event log and manual resend in the console, or your own scheduler for reminders.
Webhooks
You need hosting, certification or per-signer certificate statements
Ask us. Signatures are created server-side with the key and certificate of the application environment; anything beyond what the documentation states is answered case by case.
Contact
What IgniSign is
An e-signature API for developers and integrators: create the request from your application, let the signer sign inside your product or from a link, keep the proof. Simple and advanced levels, pay per signature, free development environment.
Create your API key
See pricing