Skip to main content

API & data · On request

Every noticeas one record.

procuris reads TED, bund.de and 90+ procurement portals, merges duplicate publications and delivers one JSON model to your CRM, ERP, BI or agent. Via REST API and webhooks, through an individual quote.

Send a requestBrowse live data

What you get

The fieldsa system needs.

Values the source did not publish are never invented. What the AI estimated is marked as an estimate.

Identity
ID, reference number, title, description, original source
Buyer
Organisations with their role, contact and address where published
Dates
Publication, submission and participation deadline, last modified
Classification
CPV codes, region (NUTS), procedure and contract type
Contract valueAI
Amount and currency, AI estimate flagged as such
Status
Lots, archive flag, data timestamp

How it arrives

One REST API,your system fetches.

You get the API through an individual quote. We agree fields, filters and cadence with you first.

  1. 01AccessYour system signs in with a token and reads over HTTPS, responses arrive as JSON. The API only reads, it writes nothing.
  2. 02FiltersBy CPV code, region, deadline, contract value and procedure type. A run fetches only what is new or changed since the previous one.
  3. 03CadenceThe data gets at most one new state per hour. Your system fetches on its own schedule, hourly or nightly for example.
Send a requestRead the API docs
{
  "id": "e9da30eb-50e6-47f1-887f-434016267b2f",
  "title": "Nordhausen - Sanierung Rolandbrunnen, Erneuerung Brunnentechnik",
  "description": "Erneuerung der Brunnentechnik des Rolandbrunnens in Nordhausen. …",
  "tenderNumber": "33/61/2026",
  "publicationDate": "2026-09-17T13:32:56.000Z",
  "submissionDate": "2026-10-07T08:00:00.000Z",
  "participationDeadline": null,
  "contractAmount": "334643 EUR",
  "contractCurrency": "EUR",
  "isAmountAiPrediction": true,
  "legislation": null,
  "organizations": [
    { "name": "Stadtverwaltung Nordhausen - Vergabestelle", "role": "contractingParty" }
  ],
  "cpvClassifications": [
    { "cpvCode": "45000000", "title": "Bauarbeiten" },
    { "cpvCode": "71000000", "title": "Architektur & Ingenieurwesen" }
  ],
  "regionCodes": [],
  "realizedLocation": null,
  "isArchived": false,
  "lastModified": "2026-09-17T13:32:56.000Z",
  "url": "/tender/e9da30eb-50e6-47f1-887f-434016267b2f"
}
One record as the API returns it. Shortened, otherwise unchanged.

Connections

Events instead of polling, or straight into your team's tools?

Webhooks

procuris reports new tenders, changes, deadlines and hits to your system on its own.

Go to webhooks

Custom workflows

Microsoft Teams, SharePoint, Confluence, Salesforce or n8n, connected for your organization one by one.

Go to custom workflows

On request

A quotefor your scope.

You get the API, webhooks and custom workflows through an individual quote. This is the way there.

  1. 01Send a requestThrough the contact form. Tell us what you want to connect, for example new hits into the CRM or a message in Teams.
  2. 02Talk about the scopeWe clarify which services you need, which systems you connect and how often your system fetches.
  3. 03Individual quoteTailored to that scope. If procuris should build the integration, the quote says so.
  4. 04SetupAfter the contract is signed, we set up access for your organization. From then on the person with the Owner role manages tokens and target addresses in procuris.

Ready?

Win yournext contract.

Book a demo or talk to us about data access.

Sign upTalk to us