Which tender data does procuris deliver?

procuris delivers public notices from Germany and the EU with title, buyer, dates, CPV and NUTS codes, procedure type, contract value, lots and original source whenever those fields are published.

Is there a tender data API?

Yes. The procuris REST API uses token authentication and scoped access. Webhooks notify your systems about new matching tenders, status changes and deadline updates. We agree the exact delivery scope for each use case.

How current is the data?

Connected sources are processed several times per day. Public detail pages and data feeds are refreshed regularly, and the record retains its data timestamp.

Can users verify the original source?

Yes. procuris retains the source platform, procurement reference and original-notice link whenever provided, keeping each record verifiable.

Who is data access for?

Companies with their own CRM or ERP, market-intelligence teams, vertical portals, consultancies and software providers integrating procurement data into products or agent workflows.

Tender data as a service

Public tender data from 90+ portals – delivered by API

procuris collects public tenders from Germany and the EU, merges duplicate publications and delivers one consistent data model to your systems. Use the REST API and webhooks for CRM, ERP, BI, vertical portals and AI agents.

Discuss data access Browse live data

Token authentication · Scoped access · Original source per record

connected procurement portals: 90+
German state portals: 16
normalised data model: 1
for delivery: REST + webhooks

Coverage

One data provider instead of dozens of point solutions

Relevant notices are spread across EU, federal, state and municipal portals. procuris handles collection, normalisation, deduplication and source attribution, giving you a consistent feed without maintaining scrapers for changing portal formats.

EU and federal sources

TED/eForms, eVergabe-Online, service.bund.de and the German Public Procurement Data Service.

States and municipalities

All 16 German state portals plus connected municipal notice and procurement services.

Cross-portal sources

Additional German procurement platforms and notice services, unified and deduplicated.

Data model

The fields your systems actually need

Each record contains the available source information and a normalised procuris view. Values not published by the source are never invented.

Identity: ID, reference number, title, notice type and original source
Buyer: Organisation, address and published contact details
Dates: Publication, participation deadline, submission deadline and data timestamp
Classification: CPV, NUTS, contract type, procedure type and legal basis
Commercial data: Estimated contract value, currency, lots and contract scope
Processing: Normalised description, source platform, status and duplicate relationship

Delivery

From the notice directly into your workflow

REST API

Token-authenticated read and write access with scopes for individual systems and teams.

Webhooks

Events for new matching tenders, status changes and deadline updates.

Traceable provenance

Original source, platform and procurement reference stay attached to each record.

Semantic enrichment

AI summaries and profile matching complement the structured procurement fields.

Use cases

For data products, sales and market intelligence

CRM and ERP: Move new opportunities, buyers and deadlines into existing processes automatically.
BI and market analysis: Analyse procurement value, regions, CPV segments and buyers systematically.
Vertical portals: Integrate relevant public contracts into your own product or customer portal.
AI agents: Ground agents in current, structured data that remains traceable to its original source.

Standards and provenance

Built on official classifications

eForms makes EU procurement notices machine-readable. procuris carries these fields forward and maps national notices into the same usable model.

Tender data questions

Which tender data does your system need?

We define sources, fields, filters, update frequency and access together, then provide a feed that fits your workflow.

Request data access