Khatm
Electronic signature, in your product.
Add PDF signing to your software, under your brand, in Arabic, French and English. Test in the sandbox; we guide you all the way to production.
- API v1
- White label
- FR · EN · AR
- PAdES
Explore the API · Try the demo
From PDF to signed document.
Upload your PDF
Drop your document or use our demo PDF.
Place the fields
Prepare each signer’s field positions.
Send for signature
Share the document and track signing progress.
Finalize
Retrieve the signed document and related evidence.
Every field. In the right place.
From the document to the fields users complete: see how fields are prepared while keeping control of their position.
Upload your PDF
The document is ready for analysis.
Find the fields
Signature areas appear.
Review and adjust
Assign fields to the right people.
Your signature. Your business.
HR software, customer portal or SaaS: signing fits into the software you build.
HR software
Offers, contracts and amendments signed inside your HRIS, under your brand, from first contact to day one.
Client onboarding
Terms, mandates, and agreements signed at sign-up, for a relationship that starts simply.
SaaS workflows
The API creates requests, webhooks track status: your product, all the way to signature.
One API to sign anywhere.
Create a request from your backend, let Khatm run the signer journey, and get the status by webhook.
Sandbox v1
Test keys and a test certificate to prototype safely.
Detection by API
Field suggestions to confirm before activation.
Signed webhooks
Completed, declined, or cancelled: every step is notified.
Signing designed with evidence in mind.
A signature rests on several evidence elements. Khatm keeps them with the file from upload through completion.
Legal value depends on the certificate, party identification, timestamping, and context. Khatm is not automatically an eIDAS qualified electronic signature.
The right references.
Signing in a SaaS
The document, signers, and tracking inside your product.
From PDF to signature
Discover each document preparation step.
Demo and production
Separate the signing journey from trust infrastructure.
FAQ
Can I integrate Khatm into my application?
Yes. The REST API creates signature requests, activates signing sessions, tracks status, and retrieves completed documents and evidence.
Can I test the API?
Yes. The Developer Sandbox lets you test the complete integration with API keys, signing URLs, webhooks and downloadable artifacts using a test certificate.
Can I use Khatm without integrating the API?
Yes. You can prepare, send and track documents directly through the Khatm platform.
Is the Sandbox a production trust service?
No. The Sandbox is intended for integration testing and currently uses a self-signed test certificate.
Do I need to create a password?
No. Account access uses an email magic link or passkey. Google sign-in appears when enabled.
How much does integration cost?
We define the scope with you: application, workflow, volumes and trust infrastructure. Contact us to scope the project before agreeing on a price and timeline.
Which document should I use to test?
Use the sample PDF offered in the form or a fictitious document without confidential data.
Why does my PDF reader not trust the certificate?
The demo uses a self-signed certificate outside any public chain of trust, so a warning is expected. In production, the certificate comes from your trust service provider. Do not turn off your PDF reader’s checks.