HomeTemplates & API

One template. Two channels.

You define a template once. It is filled in manually from the workspace or programmatically through the API. The same fields, two faces.

In short

e-doc templates follow a hybrid model: each template can be marked for the portal (manual completion, with help text and a logical field order — for ad-hoc contracts, NDAs and acceptance reports), for the API (programmatic completion, strict regex validation, JSON — for HR memos, ERP invoices and automated reports) or for both. The REST API lets you create documents from templates, upload photos, trigger signing and download sealed documents; SDKs are available for Node.js and .NET.

Templates · hybrid model

One template. Two channels.

You define a template once. It is filled in manually from the workspace (with help text and a logical field order) or programmatically through the API (with strict validation). The same fields, two faces.

Access channels
Each template can be marked for one or both channels.
Portal
Filled in manually by a user
Help text, field ordering, user-friendly validation. For ad-hoc contracts, NDAs and on-site acceptance.
API
Filled in programmatically by a system
Strict regex validation, JSON format, no help text. For HR memos, ERP invoices and automated reports.
Both
Hybrid — one source, two faces
Shared fields plus per-channel metadata. The mobile app uploads through the API, the review happens in the portal. The same data, the right interface.
POST
api.e-doc.md/v1/documents
// Create a document from the "raport-vizual" template
{
  "template": "raport-vizual-santier",
  "channel": "api",
  "folder": "rapoarte/santier-2026",
  "fields": {
    "client_idno": "1015600032841",
    "site_address": "str. Pacii 14",
    "date": "2026-05-04",
    "defects_count": 2
  },
  "signers": [
    { "email": "sef@firma.md", "order": 1 }
  ]
}

What does an API call look like?

A POST to api.e-doc.md/v1/documents with the template, the channel, the folder, the fields (JSON) and the signers with their order — the response is a 201 with the document ID. From there the signing flow runs automatically.

What integrations are possible?

Any system that speaks REST: creating documents from templates, uploading photos, triggering the signing flow, downloading sealed PDFs. Official SDKs for Node.js and .NET. Full documentation: /docs.html.

e-doc, in data

Portal channel
Manual completion · help text · field ordering · UX-friendly validation
API channel
Programmatic JSON · strict regex validation · for ERP/HR/reports
Hybrid
Shared fields + per-channel metadata · one source, two faces
API
REST — create from template, photos, signing, download sealed
SDK
Node.js · .NET

Frequently asked questions

Can I fill the same template both manually and from the API?

Yes — that's the hybrid mode: shared fields, per-channel metadata; the mobile app uploads through the API, the review happens in the portal.

Which SDKs are available?

Node.js and .NET, on top of the REST API.

Where is the API documentation?

At /docs.html — with a quick start and examples.

A personalised 30-minute demo

Drop the paper. See it in action.

See the platform with your own real documents, configured for your organization. Flexible scheduling, in Romanian or Russian.

API documentation
Published: 2026-08-19 · Updated: 2026-08-19 · Author: Intelectsoft SRL