E-signing Digital signatures eIDAS & iDIN

Custom Zynyo integration development

Appfront builds custom integrations with Zynyo (formerly ValidSign), the Dutch platform for digital signatures and e-signing. Via the Zynyo REST API and callbacks, you automatically send contracts and documents for signing — with the right eIDAS levels, iDIN identification and real-time status fed back into your own system. You save hours of manual work per file and keep a watertight audit trail.

What is a Zynyo integration?

Zynyo (formerly known as ValidSign) is a Dutch platform for digital signatures and e-signing. Documents are sent through a signing flow to one or more signers, who sign legally binding documents at the eIDAS level appropriate to the document: standard (SES), advanced (AES) or qualified (QES). For each signature, the platform records a signing certificate with a timestamp and identity details.

In practice, a custom integration means creating signing flows programmatically from a template and data from your CRM, HR or real estate system, adding signers in the right order, enforcing identification with iDIN or a qualified certificate, and automatically writing the status back to your own record via callbacks. This way the entire signing process runs without manual copying or emailing.

Appfront builds according to the official Zynyo (ValidSign) developer documentation and the OWASP ASVS security standard. We tailor templates, signing flows and error handling to your actual processes, so the integration grows with your organisation and keeps running reliably even at peak volumes.

Legally binding signatures

Documents are signed digitally and legally at the eIDAS level that matches the risk: SES, AES or QES. No printing, scanning or wet-ink signatures, just a watertight, legally usable signing certificate.

eIDAS compliance & evidential value

Zynyo complies with the European eIDAS Regulation and ETSI standards. Every signature receives a timestamp and identity details, recorded in an audit trail that serves as legal evidence in the event of disputes.

Identification with iDIN

For a higher level of assurance, the signer identifies themselves through their own bank using iDIN, or with a qualified certificate. This lets you demonstrably record who signed, which suits AES and QES signatures.

Our development process for Zynyo integrations

We follow a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your documents, signing flows and source system through to go-live and ongoing maintenance, every step is aimed at an integration that your team can understand and trust.

1
Analysis & scope

We map out which documents you want to automate, which data from your source system needs to go into the templates, how many signers there are and in what order, and which eIDAS level and identification method each document type requires.

2
Architecture

We design the integration architecture around the Zynyo REST API, choose the right authentication and callback handling, and draw up an error-handling strategy.

3
Development

Implementation with automated tests, structured logging and monitoring. You see working builds along the way.

4
Go-live & maintenance

A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.

What a Zynyo integration delivers in practice

Every Zynyo integration is set up specifically for your documents, signing flows and adjacent systems. Below are the features we most often deliver for organisations that use Zynyo (formerly ValidSign) as part of their signing process.

Zynyo REST API integration

We integrate directly with the Zynyo REST API (and the SOAP API where needed) from your CRM, HR or real estate system. Signing flows are created programmatically, documents uploaded and signers added, without anyone having to work manually in the Zynyo portal.

1 2 3

Signing flows & order

Multiple signers in a fixed order or in parallel, with automatic reminders by email or SMS if signing is overdue. Think of a contract that is first approved internally and then sent to the customer, fully automated through the integration.

Templates & prefilled fields

Document templates with fields that are filled automatically with data from your system or that the signer completes before signing. With Fast Track templates, you send standard documents in a single API call, consistently and without copying errors.

AES SES QES

eIDAS levels per document type

For each document type, we define the right eIDAS level: SES for low-risk documents, AES with strong identification for contracts, or QES with a qualified certificate for the highest level of legal certainty. The integration enforces the right level automatically.

Identification & authentication

The right identification method for each signer: iDIN via their own bank, SMS verification, or a qualified certificate from a recognised trust service provider. The chosen method is enforced in the flow and recorded in the signing evidence.

Webhooks & status handling

Callbacks from Zynyo report in real time when a document has been opened, signed, declined or expired. We set up a webhook endpoint that validates and processes events, so the file or deal status in your own system updates automatically, with no manual checks.

Typical use cases in practice

A Zynyo integration looks different in every sector. We see a number of patterns come up often, and for each of them we have a working setup that pays attention to templates, signing flows and the right eIDAS and identification level.

HR & employment contracts

HR teams that have employment contracts, addenda and onboarding documents signed digitally from their HR system. New employees identify themselves with iDIN and sign with legal validity, while the signed version ends up automatically in the personnel file. See also our API integrations.

Legal & law firms

Law firms, notaries and legal departments that have agreements, powers of attorney and settlement agreements signed with legal validity. For documents with a high burden of proof, the integration enforces AES or QES, with a watertight audit trail for every signature.

Finance & insurance

Banks, insurers, intermediaries and financial advisers that have credit agreements, policies and applications signed digitally. iDIN identification confirms the customer via their own bank, while the signed documents are retained with an audit trail for supervision and compliance.

Real estate & estate agents

Estate agents, landlords and property managers who have purchase and rental agreements, service assignments and valuation reports signed remotely. Multiple parties sign in sequence and the signed documents flow back into the file.

Technology we use

We build Zynyo integrations using the official Zynyo REST API and callbacks, combined with the backend stack that suits you. The exact choice depends on your source system and the identification levels you need, so that your own team can manage or further develop the integration.

Zynyo REST API Zynyo SOAP API Callbacks / webhooks API key authentication Transactions & packages Templates & Fast Track eIDAS SES / AES / QES iDIN identification Qualified certificates SMS verification eSeal & Long-Term Validation Node.js / Python / PHP / .NET / Java / Go Salesforce & HubSpot integrations HR & real estate systems Signature validation GitHub Actions

Why Appfront for your Zynyo integration?

Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes, because an integration must not only be technically sound but also add practical value to the way you work.

For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.

You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.

Also take a look at our broader services around API integrations, middleware, custom software and web app development. You can find an overview of all integrations on our integrations page.

  • Experience with the Zynyo (ValidSign) REST API, transactions and templates
  • Familiar with eIDAS levels, iDIN identification and signing flows
  • Specialist in integrations with CRM, HR and real estate systems
  • Secure by default: API key rotation, callback validation, scoped permissions
  • Structured error handling and retry mechanisms
  • Extensive logging and monitoring from day one
  • Clear documentation that your team can read and maintain
  • A single point of contact, no passing you between account managers
  • Ongoing maintenance and proactive further development
  • An approach tailored to your existing IT landscape

Security and privacy in Zynyo integrations

Documents that are signed digitally almost always contain personal data or commercially sensitive information. Appfront builds to the OWASP ASVS security standard. Among other things, that means API keys in secure vaults, validation of incoming callbacks, scoped permissions per integration, separate test and production environments, and regular audits of the signing flows.

Zynyo is a Dutch platform that operates in line with the European eIDAS Regulation and ETSI standards, and is ISO 27001 certified. For every signature, the platform records a signing certificate with a timestamp and identity details — the audit trail that secures the burden of proof and serves as legal evidence in a dispute. We document the data flows, templates and identification methods so that your record of processing activities is complete and you can demonstrably comply with the GDPR.

More about our approach to security: information security policy and CVD policy.

  • GDPR-compliant data processing and minimisation
  • Encryption in transit (TLS 1.2+) and at rest
  • Role-based access and least-privilege principles
  • Audit logs with traceable data flows
  • Automatic retry and dead-letter queues
  • Monitoring and alerting for anomalies
  • Secrets management following best practices
  • Documentation for your record of processing activities

Frequently asked questions about Zynyo integrations

Answers to the questions we are asked most often about Zynyo (formerly ValidSign) integrations.

A Zynyo integration is a technical integration between Zynyo (formerly ValidSign) and another system — such as your CRM, HR platform, property software or in-house application. Via the Zynyo REST API, signing flows are created programmatically from templates, populated with data from your system and sent to one or more signers. Callbacks (webhooks) report the status back in real time as soon as a document has been signed, declined or has expired. An integration can be simple (sending a single contract template) or extensive (multiple signers in sequence, iDIN identification and archiving with an audit trail).

Zynyo is the current brand name of the Dutch e-signing platform that previously operated as ValidSign. The underlying SigningService, the REST API and the developer documentation are the same technology. Anyone who previously built a ValidSign integration is effectively working with the same platform under the name Zynyo. Appfront builds both new Zynyo integrations and integrations that originated under the ValidSign name.

Zynyo supports all three eIDAS levels: the standard electronic signature (SES), the advanced electronic signature (AES) and the qualified electronic signature (QES). Which level is appropriate depends on the legal risk of the document and the burden of proof you need. In the integration, we define for each document type which level and which identification method — for example iDIN for AES or a qualified certificate for QES — is enforced.

With iDIN, a signer identifies themselves through their own bank's login, which confirms who the person is. In the integration, we configure each signing flow so that iDIN identification is required before anyone may sign. Zynyo also supports other identification methods such as SMS verification and qualified certificates. Together with you, we choose the right method per document type, so that the identity is demonstrably recorded in the audit trail.

Zynyo sends callbacks (webhooks) whenever the status of a signing flow changes — for example when a document has been opened, signed, declined or has expired. Appfront sets up a webhook endpoint that receives these events, validates them and processes them in your own system. This way, for example, the case status in your CRM or HR system updates automatically and nobody has to track the status manually.

We work with the official Zynyo REST API (and the SOAP API where necessary), combined with the backend stack that suits you — Node.js, Python, PHP, .NET, Java, Ruby or Go. For the signing flows we use transactions, packages and templates; for status processing, the callback mechanisms. Authentication runs via an API key. We handle identification with iDIN or a qualified certificate, depending on the required eIDAS level.

The cost depends on the complexity of the signing flows, the number of signers and their order, the number of systems to integrate, the identification levels you need and the amount of custom business logic. Ongoing maintenance, monitoring and support also play a part. We always provide a clear quote after a no-obligation analysis of your situation.

Yes. Appfront regularly takes over the maintenance of existing Zynyo or ValidSign integrations, even if they were originally set up by another party. We review the API integration, templates, signing flows, callback configuration and error handling, document the current setup and draw up improvement proposals. From then on we handle changes, extensions and monitoring, including timely API key rotation.

Ready to build your Zynyo integration?

Tell us which documents you need signed and which system Zynyo (formerly ValidSign) should integrate with. We're happy to advise on signing flows, eIDAS levels, iDIN identification and status handling via callbacks. A no-obligation first conversation will give you a clear picture of the possibilities within half an hour.

Edit content