Your signature. Your way of working.

Four use cases, one engine.

SaaS, customer portal, HRIS or ERP: signing fits into the software you build.

SaaS & software

Add signing to your product, in an interface that stays yours.

• Terms of service
• Subscription
• Amendment

REST API + signature_request.completed webhook

A subscription agreement signed without leaving your software. Create the request from your backend, show the signing link in your interface, then receive the status and files by webhook.

Customer onboarding

Collect agreements at the right moment, from day one of the relationship.

• Agreement
• Mandate
• General terms

Multiple signers, in the order you set

A signed agreement to start the customer relationship. Link the request to the customer file, guide each signer and retrieve the finalized document at the end of sign-up.

HR software

Offers, contracts and amendments signed in your HRIS, without leaving your interface.

• Employment contract
• NDA
• Amendment

Reusable templates + white label

An employment contract signed from the employee record. Create the request from the employee file using a template, then attach the signed contract and its evidence to the record.

CRM, ERP & business tools

Connect signing to your CRM, ERP or custom tools.

• Quote
• Purchase order
• Master agreement

client_reference + signed webhooks

A signed quote, attached to its record in your CRM. Use a business reference to link each request to its record. Signed webhooks keep your application up to date.

One request, two ways to drive it.

Every step exists in the interface and in the API. Your teams and your product work on the same requests.

Prepare

Platform : Upload the PDF, add signers and place the fields.

API : POST /v1/signature-requests

Collect signatures

Platform : Send the links and remind pending signers.

API : POST /v1/signature-requests/{id}/activate

Retrieve

Platform : Download the signed PDF and evidence from your workspace.

API : GET /v1/signature-requests/{id}/artifacts/{type}

Start with the interface or with code.

Get started with no development, or build signing into your application. Both run on the same engine.

To test and manage.

The Khatm interface to try the flow, prepare your templates and track requests, with no development.

• Prepare PDFs from the interface
• Organize signers and fields
• Find every file in one place

For your product.

Your interface, your backend, your workflow. Signing fits into your experience.

• Create requests from your application
• Show the signing link in your interface
• Receive events through signed webhooks

The same foundation. For every request.

Well-prepared documents, clear tracking and evidence to keep at the end of every request.

Field preparation

Signature, initials, date or text, placed by hand or suggested by detection.

Multiple signers

Each signer gets their own link and only fills their own fields, in the order you set.

Status tracking

Prepared, active, completed, declined or cancelled: the state of every request, at any time.

Signed PDF

The finalized document, downloadable from the interface or through the API.

PDF and JSON evidence

A readable evidence file and its JSON version for your records.

API sandbox

Test keys to prototype the integration before production.

The public demo produces a genuinely signed PDF, with a test certificate. The API sandbox lets you test the integration with your own keys.

From demo to production.

The sandbox is there to validate your integration. Going live is prepared with you, based on your market and requirements.

Sandbox · Today

Test keys and certificate, files deleted 10 days after upload. Built for developing and validating the integration.

Scoping · Together

Your use case, volumes, the expected signature level and how long documents must be kept.

Production · Next

Your trust service provider’s certificate, retention agreed with you and a guided rollout.

Khatm is not a qualified trust service provider: legal value depends on the certificate and identification chosen for your project.

Build signing into your business.

From preparing the document to retrieving the files, the key steps to build signing into your application.

Prepare the file

Attach the PDF, signers and fields to a stable business reference (client_reference). It lets you find the request in your application.

Support the signer

Show the signing link at the right moment in your application. Present the document and the expected actions clearly.

Update your application

Use webhooks to track the request status, then attach the documents and evidence to the original record.

Ready to add signing? Start in the sandbox.

Create an account to get your test keys, or tell us about your project.

Discuss my integration