Custom TenderNed integration development
Appfront builds custom integrations with TenderNed, the Dutch government's tender platform. We connect the open tender data and the TenderNed API (eForms XML and the TNS publication web service) to your own software, bid management or analytics environment. This lets bid teams spot relevant tenders automatically, lets you run market analyses on public procurement data, or lets you publish notices as a contracting authority via the import integration.
What is a TenderNed integration?
TenderNed is the Dutch government's public procurement platform, part of PIANOo and the Ministry of Economic Affairs. All government tender notices, from market consultations and prior information notices to contract awards and modifications, are published here. This procurement data is public: anyone can consult the publications, and organisations can retrieve them automatically to process in their own software.
A custom integration in practice means: reading the historical datasets (Excel and JSON) and the TenderNed API (current notices in XML, eForms format), normalising the publications by CPV code, region and notice type, filtering for what matters to you, and passing the results on to your bid management, CRM or database. For contracting authorities it works the other way round: publishing notices from an in-house procurement system via the import integration.
Appfront builds on the official TenderNed open data and API and the OWASP ASVS security standard. We tailor the filter logic, error handling and retrieval frequency to your actual processes, so the integration grows with your organisation and stays reliable even with large data volumes. For API access we use the username and password provided by TenderNed.
Open procurement data
Government tender notices are public. Historical datasets are available in Excel and JSON, and current publications can be retrieved via the TenderNed API in XML (eForms). No more manual searching: the data flows into your system in a structured form.
Targeted tender alerts
Filter by your CPV codes, region, contracting authority and keywords, so that only relevant tenders come through. Bid teams receive an automatic signal when a promising new tender appears and no longer miss a deadline.
Publishing via the import integration
Are you a contracting authority? Then you publish notices from your own procurement system via the import integration. TenderNed then automatically forwards European tenders to TED, the European publication platform.
Our development process for TenderNed integrations
We work to a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your information needs, the right data source (open data, API or import integration) and your target system, through to go-live and ongoing management, every step aims for an integration your team can understand and trust.
We map out which tender data you need, which CPV codes, regions and notice types you want to filter on, which target system receives the data, and whether open data, the API or the import integration is the right route.
We design the integration architecture, arrange API access with TenderNed, choose the retrieval frequency and set up an error handling and recovery strategy.
Implementation of reading and processing the eForms XML, with automated tests, structured logging and monitoring. You will see working builds along the way.
Controlled go-live with data validation and safeguards, followed by ongoing management, including keeping pace with changes to the TenderNed interface and the eForms standard.
What a TenderNed integration delivers in practice
Every TenderNed integration is tailored to your information needs, processes and adjacent systems. Below are the capabilities we most often deliver for organisations that want to use tender data structurally in their work.
Tender monitoring and alerting
Continuous monitoring of TenderNed publications, filtered by your CPV codes, region, contracting authority and keywords. Relevant tenders appear automatically in your own software, with alerts by email, dashboard or a notification in your CRM, so your bid team misses nothing.
Processing eForms XML
We read from the TenderNed API and process the notices in XML, the eForms format that TenderNed also uses for publication to Europe. The fields are mapped to a clean data model, so your application can work reliably with the tender data.
CPV & metadata filtering
Smart filtering on CPV codes (the European product classification for contracts), notice type, estimated value, contracting authority and place of performance. This way you only keep the tenders that truly fit your qualifications and strategy.
Import integration for publication
For contracting authorities: offering notices from your own procurement system to TenderNed via the import integration. European tenders are then automatically forwarded to TED. One source, double publication without double work.
Integration with bid management and CRM
Tenders found flow directly into your bid management or CRM as qualifiable opportunities, with deadline, contracting authority and document links. Your team works from a single environment and keeps the full pipeline from identification to submission clearly organised.
Market analysis & reporting
Build analyses on the historical datasets: which contracting authorities award which contracts, in which regions, at which estimated values, and to which market parties. Trends and opportunities become visible in dashboards that follow your own questions.
Typical use cases in practice
A TenderNed integration looks very different from one organisation to the next. We see a number of recurring patterns, and for each we have a working setup that pays close attention to the right data source, filter logic and the target system that receives the tender data.
Bid teams at government suppliers
Companies that regularly bid on government contracts and don't want to miss a winnable tender. The integration automatically spots relevant publications based on your CPV codes and region, and feeds them into your bid management as qualifiable opportunities. See also our eHerkenning integration for logging in to business platforms.
Market research & consultancy
Researchers and advisers who analyse tender data: which contracting authorities buy what, at which values and from which suppliers. We open up the historical datasets and build repeatable reports and dashboards around your own research questions.
Contracting authorities & procurement
Municipalities, water boards and other contracting authorities that publish from their own procurement system. Through the import integration, notices are placed on TenderNed and European contracts are submitted to TED automatically, without your buyers having to enter the same data twice. We build this as part of your software for municipalities or custom water board software.
Software vendors & SaaS
Providers of tender, procurement or market intelligence software that want TenderNed data as a feature in their product. We build the integration as a robust layer beneath your application, with proper error handling and monitoring, so tender data is reliably available in your platform. You might also consider our grant management software for related public sector data streams.
Technology we use
We build TenderNed integrations using the TenderNed API (XML, eForms format) and the TNS publication web service (JSON), combined with the backend stack that suits you. The precise choice depends on your target system and data volume, so that your own team can manage or further develop the integration.
Why choose Appfront for your TenderNed 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. An integration should not only work technically, but also add practical value to the way you work.
With every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage it. 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. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.
You may also be interested in our wider services around custom software, AI for municipalities and government and software for housing associations. Would you rather talk it through directly? Get in touch.
- Experience with the TenderNed API, open data and eForms XML
- Specialists in integrations with bid management, CRM and analytics environments
- Experienced with CPV classification, tender data and the import integration
- Secure by default: credentials in secure vaults, encrypted connections, scoped permissions
- Structured error handling and retry mechanisms
- Comprehensive logging and monitoring from day one
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Ongoing maintenance and proactive further development
- A way of working aligned with your existing IT landscape
Security and privacy in TenderNed integrations
Tender data itself is public sector open data, but your own qualifications, bid strategy, filter profiles and contact details are not. Appfront builds to the OWASP ASVS. This means, among other things: TenderNed API credentials kept in secure vaults, encrypted connections (TLS), scoped permissions and regular audits of the data flows.
We document the data flows, integration points and target systems so that your record of processing activities is complete and you can demonstrate compliance with the GDPR. Where the integration touches personal data, such as contact persons at contracting authorities or bidders, we apply data minimisation, purpose limitation and clear retention periods.
Also see our SURFconext integration and Azure AD integration for secure access and authentication within government and education contexts.
- GDPR-compliant data processing and data minimisation
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Automatic retries and dead-letter queues in the event of API outages
- Monitoring and alerting for anomalies
- Secrets management in line with best practice
- Documentation for your record of processing activities
Frequently asked questions about TenderNed integrations
Answers to the questions we are asked most often about TenderNed integrations.
A TenderNed integration is a technical link between TenderNed and your own software. TenderNed is the Dutch government's tendering platform, part of PIANOo and the Ministry of Economic Affairs. Public procurement notices are available as open data: historical datasets in Excel and JSON, and current publications via the TenderNed API in XML (eForms format) and the TNS publication web service in JSON. We connect that data to your bid management, CRM or analytics environment, so relevant tenders come in and are processed automatically.
Tender data published on TenderNed is public. Anyone can download the historical datasets (Excel and JSON) without logging in, and the TenderNed API lets you retrieve current notices in XML. For API access, you will need to request a username and password from functioneelbeheer@tenderned.nl. The import integration (eSender route) is intended for contracting authorities and their procurement systems: it allows you to publish notices from your own system to TenderNed, after which European tenders are automatically forwarded to TED. We will work with you to determine which interface suits your role.
Yes. We build monitoring that periodically reads TenderNed publications, filters them by your CPV codes, region, contracting authority and keywords, and automatically flags relevant tenders in your own software. Bid teams receive alerts by email, dashboard or a notification in your CRM, so no promising opportunity goes unnoticed. We align the filter logic with your actual qualification criteria and deal flow.
We work with the TenderNed API (XML, eForms format) and the TNS publication web service (JSON), combined with whichever backend stack suits you — Node.js, Python, PHP, .NET, Java or Go. For API access we use the username and password provided by TenderNed. We process eForms- and TED-compliant XML, normalise CPV codes and notice types, and make the data available through a clean interface to your own system or database.
The cost is determined by the complexity of the data flows, the number of systems to be integrated, the desired retrieval frequency, and the amount of custom work in the filtering and processing logic. Ongoing management, monitoring and support also affect the total investment. We always provide a clear quote following a no-obligation analysis of your situation.
Tender data is public government data, but your own qualifications, bid strategy and contact details are not. Appfront builds according to OWASP ASVS: API credentials in secure vaults, encrypted connections, scoped permissions and strictly separated access per integration. We document the data flows so your record of processing activities stays complete and you can demonstrate GDPR compliance. Where the integration touches personal data, we apply data minimisation and retention periods.
Yes. Appfront regularly takes over existing integrations, including those originally set up by another party. We review the API calls, the processing of the eForms XML, the filtering logic and the error handling, document the current setup, and propose improvements. From that point on, we handle changes, extensions and monitoring, including keeping pace with changes to the TenderNed interface and the eForms standard.
A TenderNed integration is valuable for suppliers to government that track tenders with a bid team, for market researchers and consultants who analyse tender data, and for software vendors who want to add tender monitoring or market intelligence to their product. For contracting authorities and their procurement systems, the import integration is relevant for publishing notices from their own system. We determine case by case whether you need the open data, the API or the import integration.
Ready to get your TenderNed integration built?
Tell us which tender data you want to process and which system TenderNed needs to connect to. We are happy to help you choose the right data source, filtering logic and target system. Book a no-obligation advisory session and you will get a clear picture of the options for tender monitoring, market analysis or publication via the import integration.