What developers build with the IgniSign API
A signing step inside a flow your product already owns. The level and the mode are choices you make per signature profile.
Teams use the IgniSign API to add a signing step to a flow their product already owns: a contract in a SaaS, a mandate or consent in a fintech onboarding, a lease in a proptech, an employment contract in an HR tool, a policy in an insurtech, an enrolment form in education software. Each case is a signature request created from the application, signed inside the product or from a link, with the proof returned to the application.
The signature level suggested for each case is a common practice of teams using the API, not legal advice: the legal effect of a signature depends on the applicable law and on your use case.
SaaS and platforms
Documents: Terms, order forms, service agreements and consents generated by the product itself.
Who signs: Your users, already logged in.
Integration: Embedded signing page inside the application; webhook on completion; proof stored with the account.
Level: Simple for acknowledgements and low-risk agreements, advanced when who signed matters.
Fintech and banking software
Documents: Account opening mandates, loan or investment agreements, direct-debit authorisations.
Who signs: Customers during onboarding, often on mobile.
Integration: Embedded page in the onboarding flow, or a hosted link sent by email; identity verification through open banking or an ID document check when the flow requires it.
Level: Advanced, with a second factor or an identity verification recorded in the proof.
Insurance software
Documents: Policy subscriptions, renewals, claims declarations, terminations.
Who signs: Policyholders and brokers.
Integration: Hosted link for policyholders, embedded page for broker portals; webhooks feed the policy status back into your system.
Level: Simple for declarations, advanced for subscriptions and terminations.
Proptech
Documents: Leases, inventories, mandates, offers and sale agreements with several parties.
Who signs: Tenants, landlords, agents, buyers and sellers.
Integration: Several signers on one request, in order or in parallel; hosted links for external parties; the signed PDF and audit log returned to your platform.
Level: Advanced when identity matters; simple for inventories and acknowledgements.
HR and recruiting software
Documents: Offer letters, employment contracts, temporary and fixed-term contracts, onboarding forms.
Who signs: Candidates and employees, and the employer's signatory.
Integration: Hosted link emailed to the candidate, embedded page in the employee portal; webhook when both parties have signed.
Level: Advanced with a one-time SMS code is a common choice for employment documents.
Legal-tech
Documents: Engagement letters, powers of attorney, settlements, corporate resolutions prepared by the platform.
Who signs: Clients and counterparties invited by the professional.
Integration: Hosted links with the firm's branding; signature files and audit log kept with the matter; bare signature when the document must never leave the firm's systems.
Level: Advanced with identity verification for documents where who signed must be evidenced.
Education software
Documents: Enrolment forms, internship agreements, consents, attendance and grade acknowledgements.
Who signs: Students, parents, institutions and host companies.
Integration: Hosted links in the institution's language, several signers per agreement, bulk sending from your back office through the API.
Level: Simple for acknowledgements, advanced for agreements with third parties.
Start with the API
Quick start
Signature levels
Create your API key
See pricing