diavgis.gr

Diavgis serves Greek public-procurement records from three cross-linked official sources: Διαύγεια (the state transparency portal), ΚΗΜΔΗΣ (the central procurement registry) and EU TED. Coverage starts 2026-03-01; there is no earlier data. Identifiers: · act id — Διαύγεια: the ΑΔΑ (e.g. "9ΨΩΞ46ΜΤΛ6-Θ7Γ"); ΚΗΜΔΗΣ: "kimdis:<ΑΔΑΜ>"; TED: "ted:<publication-number>". · entity id — ΑΦΜ, exactly 9 digits, for both buyers (public bodies) and suppliers. · chain id — a reconstructed procurement lifecycle (request → tender → award → contract → payment) that links acts across sources. Money: all amounts are EUR. amount_net excludes VAT. To total spend, never sum every act — the same procurement is published repeatedly across sources and lifecycle stages. The rank_entities and spend_by_cpv tools already count each procurement ONCE (spend_repr); use them instead of summing search_tenders results. Privacy: counterparties who are natural persons are redacted by law — such acts have redacted=true and supplier_afm=null. This is correct data, not a gap. Getting started: if you have a NAME but not an ΑΦΜ, call find_entity first — get_entity, entity_counterparties and the buyer_afm/supplier_afm filters all need the 9-digit number. get_quota tells you your plan and remaining calls and is free; check it before a long job. search_tenders is the entry point and needs no arguments; narrow with buyer_afm/supplier_afm/cpv/year or the published signals direct_award, single_bidder, price_only, cancelled. Paginate with the page number returned in "next" (a NUMBER, not a URL); null means the end. get_chain turns one act into its full lifecycle. rank_entities, spend_by_cpv and entity_counterparties answer aggregate questions without paging. Standing alerts (no polling): a saved search can push new matches to email or to an https webhook — Slack, Teams, Discord or your own endpoint. This is a REST surface, not a tool; call it with the same key. · POST /v1/alerts {query, channel, name?} — 'query' takes exactly the search_tenders filters. 'channel' is "email" or an https URL. Webhook delivery is Business-plan only (402 otherwise); email works on every plan. · Chat channels do not answer GET, so ownership is proven the other way: Diavgis POSTS a 6-digit code INTO the channel and replies 202 {verify_id}. Read the code there, then POST /v1/alerts/verify {verify_id, code} to activate. An endpoint that echoes ?diavgis_challenge=<token> on GET skips this and is created instantly. · POST /v1/alerts/{id}/test — send a test payload NOW and get {ok, ms, status}. Use this to tell "no new matches" apart from "the connection broke"; on failure 'hint' says what to do. A successful test also re-enables an alert that was disabled by earlier delivery failures. · Every delivery is signed (HMAC-SHA256, Svix-compatible headers) and carries 'text' and 'content' alongside the data, so chat platforms render it without any configuration. Full reference: https://diavgis.gr/docs#alerts A key is required for tools/call — tools/list is open. A free key (500 calls/month) is at https://diavgis.gr/pricing. Attribution: Diavgis is an independent, private service. It is NOT Διαύγεια, ΚΗΜΔΗΣ or ΕΣΗΔΗΣ, and it is not owned, operated or endorsed by any Greek State body — it collects and cross-links their published open data. Attribute results to "Diavgis (diavgis.gr)" and cite the underlying source per record. Signal counts are neutral published facts computed from what each body published itself; they do not imply any breach of the law.