REST API Architecture
Integrate your signing processes into your own web, mobile or desktop applications easily with a JSON-based, platform-independent REST API.
Connect e-signature, mobile signature and digital signature processes to your systems with the Dijital Belge API solution. Create documents programmatically, open them for signing, track and archive them. Digitize your corporate processes quickly with a platform-independent REST API architecture.
Manage the entire document creation, signing and storage process with a single integration.
Integrate your signing processes into your own web, mobile or desktop applications easily with a JSON-based, platform-independent REST API.
Manage e-signature, mobile signature, NFC identity signing, OTP, e-mail, SMS and initial signature methods through a single API.
Turn frequently used contracts and forms into templates; generate ready-to-sign documents instantly with dynamic data via the API.
Define multi-signer and sequential signer scenarios, approval steps and reminders in code or manage them from the panel.
Add a timestamp that supports legal validity to every signing transaction; store documents and audit records securely.
Automate your processes by sending instant notifications to your system when signing is completed or a step advances.
Automate all business processes that require signatures via the API.
Automate the signing of hiring contracts, payroll and HR documents.
Digitize loan, account opening and customer acceptance processes.
Sign policy and proposal documents quickly and verifiably.
Open lease and sales contracts for remote, secure signing.
Manage consent forms and patient documents with digital signature.
Connect your EDMS and internal approval flows to the e-signature infrastructure.
Automate signature flows inside your ERP, CRM, HR and accounting systems end-to-end with a single API. The scenarios below can be implemented exactly with the sample requests in the documentation.
The purchase request approved in the ERP turns into an order and supplier contract and is opened for signing via the API. The supplier signs with e-signature and the result is written back to the ERP via webhook.
When an opportunity is won in the CRM, the proposal/contract template is filled with data and sent to the customer for signing with one click; the signature status is written to the opportunity record.
The hiring contract, confidentiality undertaking and payroll are generated in bulk and sent to employees for signing; the highest assurance level can be used for the contract and a lower level for the payroll.
In remote customer onboarding, identity verification with TCKK NFC, face recognition and location/device evidence are collected; contracts are signed in the same flow.
The courier or driver opens the delivery report on their tablet/phone in the field with Sümen Mobil; the recipient approves with NFC identity or OTP, and the evidence flows to the center instantly.
Reconciliation letters, statement approvals and payment instructions are opened for bulk signing with ERP integration; when signing is completed, the collection/payment process is triggered.
Create your Dijital Belge account and generate your dedicated API key.
Connect the signing flow to your system with the sample requests in the documentation.
Send the document or template via the API and define the signers.
When the signature and approval are completed, transfer the result to your system via webhook.
A standard signing flow can be integrated in a few days on average thanks to ready-made samples and documentation. For complex and institution-specific scenarios, the process is planned on a project basis.
The REST API is compatible with all languages that can send HTTP requests (Java, C#, PHP, Python, Node.js, etc.). It works platform-independently.
Yes. The credits consumed vary by method: e-signature, mobile signature, e-mail and SMS/OTP approval consume 1 credit; TCKK (identity) approval and TCKK + face recognition consume 2 credits; TCKK + face recognition + video onboarding consume 3 credits. You can review current credit packages on our pricing page.
E-signature produces the same legal consequences as a wet signature under Law No. 5070 on Electronic Signatures. Signatures made with qualified certificates are legally valid.
Yes. Upload your Word/PDF templates; define dynamic fields, merge them with data via the API and generate ready-to-sign documents.
Set up your first signing flow in minutes with the sample requests in our API documentation. You can reach our technical team via contact.