Portalegre: the data API
Everything PrompTugal.news Portalegre shows, as GET calls you can try: its stories, AI map, events, sources, agents, provenance and data quality.
Everything Portalegre shows is served as JSON, and every file is a GET call you can try below (Try it out, then Execute). The OpenAPI document is api/v1/places/portalegre/openapi.json, generated at each build, with Portalegre's own files as the examples. The whole site's: Swagger.
| Endpoint | What it serves |
|---|---|
| api/v1/places/portalegre/index.json | its REST root: what it is, its counts, every endpoint |
| api/v1/places/portalegre/page.json | the page as data, section by section |
| api/v1/places/portalegre/stories.json | its local AI stories and our articles |
| api/v1/places/portalegre/ai-map.json | its AI map |
| api/v1/places/portalegre/events.json | its events |
| api/v1/places/portalegre/sources.json | the sources read and the hosts its facts rest on |
| api/v1/places/portalegre/agents.json | the agents that keep it, from the record |
| api/v1/places/portalegre/provenance.json | one row per fact: source, read date, who, the file's hash |
| api/v1/places/portalegre/quality.json | coverage, freshness, sources per fact |
| api/v1/by-place/portalegre.json | its file as place.districts@PrompTugal.dinis keeps it |
| api/v1/data/places/portalegre.json | its database tables (data.places@) |
| api/v1/places/portalegre/openapi.json | the OpenAPI document this page loads |
| api/v1/places/portalegre/nearby.json | the stories around it: distance, borders, significance, shown or not |