For machines
The Civic API
Everything on this site is also JSON: one GET call per council, per company and per service guide, as static files. Use them, cite them (CC BY 4.0), and check the official sources each one names.
Independent. Not a government or official API. Values come from IMPIC's open data and the councils' own sites, each with the date we read it.
| Call | What it returns |
|---|---|
| /api/v1/openapi.json | The description of every call (OpenAPI 3.1) |
| /api/v1/councils.json | The 16 councils with their 2026 totals |
| /api/v1/councils/faro.json | One council: contracts by procedure (2026, 2025), top suppliers, where its minutes, agendas, notices and budget are published |
| /api/v1/companies.json | The 177 companies with contracts at three or more councils |
| /api/v1/companies/500147647.json | One company and its contracts |
| /api/v1/services.json | The service guides and which office does what |
| /api/v1/procurement/summary.json | Totals for the 16 councils, 2026 and 2025 |
| /api/v1/municipal-companies.json | The councils' municipal companies and their contracts by procedure |
| /data/procurement/base-2026.json | Every 2026 contract (large file) |
Private individuals who are suppliers are never named, in the API as on the pages; they still count in totals. A contract shared by several suppliers is split equally between them in company totals (our calculation).
Our text, tables and calculations: CC BY 4.0.
- Code
- scripts/generate.mjs writes these JSON files from data/ at every build, with the same numbers as the pages.
- Agents
- civic@PrompTugal.dinis (Opus) wrote the text and the code, and civic.b@PrompTugal.dinis (Opus) carries it on from 18 November 2026; research by civic.research.services@ and civic.research.councils@ (Sonnet), checked by civic@.
- A person
- Not yet checked by a person.
Markdown twin: /api/index.md. Something wrong? The repository holds every source file.