API and MCP
Building permits from Diavgeia (e-Adeies) as structured data, through a REST API or MCP. Same data and same permissions as the app: your plan's prefectures and features apply here too.
Access
The API and MCP are available on the subscription plans. The organisation's admin creates a key in Settings → API, with “read only” or “read and write” access. The key always goes in a header, never in the URL.
REST API
JSON, cursor pagination (up to 50 rows per page and up to 1,000 records per search — narrow the filters for more). Errors: { error: { code, message } }.
curl -sG "https://bouldoza.com/api/v1/permits" \ -H "Authorization: Bearer $BOULDOZA_KEY" \ --data-urlencode "municipality=Γλυφάδας" \ --data-urlencode "q=pool" \ --data-urlencode "limit=10"
Read
| Method | Path | What it does |
|---|---|---|
| GET | /me | Plan, the plan's prefectures, this month's remaining usage, what is allowed. |
| GET | /regions | Prefectures and municipalities as written in the database. |
| GET | /permits | Search acts with filters (type, area, period, sizes, pool, uses, free text q). |
| GET | /permits/{ada} | Act record. |
| GET | /projects/{id} | Project: every act on the same property. |
| GET | /engineers | Engineers ranked by activity (subscribers). |
| GET | /engineers/{id} | Engineer profile (subscribers). |
| GET | /companies | Companies as project owners or designers (subscribers). |
| GET | /companies/{id} | Company profile (subscribers). |
| GET | /stats | Totals by type, month and municipality. |
Lists, alerts and follows
Changes are made as the user who created the key, with the same plan limits as in the app, and are logged.
| Method | Path | What it does |
|---|---|---|
| GET · POST | /lists | The organisation's lists · new list. |
| GET | /lists/{id} | A list with its items. |
| POST · DELETE | /lists/{id}/items | Add / remove acts (up to 100 ADAs). |
| GET · POST | /alerts | Alerts about new acts · new alert. |
| GET · PATCH · DELETE | /alerts/{id} | One alert: change filters, frequency, time, or delete. |
| GET · POST · DELETE | /follows | Follow an engineer, project or municipality. |
OpenAPI specification · https://bouldoza.com/api/v1
Claude and MCP
The MCP server gives Claude tools to search permits, projects, engineers, companies and statistics and — with write access — to manage lists, alerts and follows. Claude asks for confirmation before anything is deleted.
https://bouldoza.com/api/mcp
- Claude.ai: Settings → Connectors → Add custom connector with the server URL. You sign in to Bouldoza and choose the organisation and access — no key needed. Revoke the connection from Settings → API.
- Claude Code / Claude Desktop: with an API key in the Authorization header.
claude mcp add --transport http bouldoza https://bouldoza.com/api/mcp \ --header "Authorization: Bearer bz_live_…"
The data
Regular acts only (no duplicate postings or revoked acts). A field not extracted with confidence is null. The owner is shown only when it is a company.