Shipping daily
Nov 9SHIPPEDFull working test of the site (checks, tools, accounts, feeds, API): a saved X-ray now shows in your dashboard, project pages have a Save to my list button again, and the update feed is currentNov 9SHIPPEDSecurity hardening: pages now refuse inline script handlers, links built from third-party data cannot run scripts, the map and text-reading libraries are pinned with integrity hashes, and payment-check lookups are rate limitedNov 9SHIPPEDSpeed: the browser no longer restyles the whole page after every small change, project and developer pages are answered from an edge copy before any data is read, sections far from the screen are drawn as you get near them, and the open numbers page keeps its figures for a minuteNov 9SHIPPEDLookalike websites: a daily watch for new websites whose names resemble the developer and project websites we track, with registration and certificate dates, on developer pages and at /watch/lookalikes/Nov 9DATASanctions lists: developer company names are screened daily against the entity entries of the OFAC, UK and UN lists; developer pages show the lists and date when there is no matchNov 9DATACorporate family on developer pages: parents and subsidiaries from the GLEIF register (CC0) for 39 developers matched by exact legal name, and a new family link type in the developer graphNov 9DATATwo Birmingham project pins corrected (they sat one degree too far north); their map-based sections stay hidden until the next monthly rebuild uses the new pinsNov 9SHIPPEDProtected land near the pin on 125 project pages: Natura 2000 sites within 2 km, England green belt and other designations, the Spanish coast law easements and mapped nature reserves, with distances and layer datesNov 9SHIPPEDThe map's own history at each plot: when the buildings, roads and land use within 150 m were first drawn in OpenStreetMap and last changed, as a small timeline on 125 project pagesNov 9SHIPPEDSite check on 560 page views and 3,078 links: the two account checks merged into one, clearer tool descriptions and jump links, a country search, an accessible pricing table and a tidier free check on phonesNov 9SHIPPEDShort-let reality check on 28 project pages: Inside Airbnb listings within 1 km, median nightly price and their occupancy estimate, next to any rental yield the page we track printsNov 9DATARecorded sale prices within 1 km on 14 project pages: HM Land Registry (England), DVF (France) and NYC rolling sales, medians and price per m2 next to the developer's own headline priceNov 9SHIPPEDProject and developer pages are easier to read: identical price copies merged into one row, the overdue date sits next to the date it is about, correct singular wording, Arabic names no longer flip punctuation, and the website-health method is translatedNov 9SHIPPEDAny plot from space: pin any spot and get one clear Sentinel-2 picture per quarter since 2017, made on demand, and turn it or a project's time machine into a shareable time-lapse GIFNov 8DATASatellite images back to January 2017: the monthly Sentinel-2 series on 125 project pages now covers almost ten yearsNov 8SHIPPEDSee the site: open street-level photos within 200 m of the pin on 59 project pages, and a 3D view with terrain and 12,328 mapped buildings on 125
Changelog →

Kolaboro / Docs / API keys

API keys and usage

The open data API needs no key and stays that way. A key gives you a usage panel, a daily quota you can plan around, and a way for us to raise your limits. We show the key once and store only its SHA-256.

Checking whether self-serve keys are open…

Create a key

No account and no email needed. Three keys an hour per visitor.

Usage panel

The key is sent only in the x-api-key header to kolaboro.com and kept in this tab's memory, never in storage.

Plans and limits

PlanDaily quotaHowPrice
No keyFair use of /api/open/*Just call itFree
Free key1,000 metered calls a day (UTC)Self-serve on this pageFree
PartnerAgreed with youWrite to hello@kolaboro.comContact us

Billing is not decided. Today we only meter calls and enforce the quota: nothing is charged and there is no card to enter. If paid plans come, they will be announced on the changelog before anything changes for existing keys.

The pilot API (document reading, desk reviews, Bitcoin timestamps, shared cases) keeps its own kb_pilot_ keys and its 200 calls a day.

Using a key

Send it in the x-api-key header to the metered base URL https://kolaboro.com/api/x/k/m/. Every path of the open API works there and returns the identical, signed body; each answer also carries x-ratelimit-limit and x-ratelimit-remaining. Over quota you get 429 until midnight UTC.

curl -H "x-api-key: kb_live_…" https://kolaboro.com/api/x/k/m/projects?market=Bali // TypeScript (see /docs/sdk/) const k = new Kolaboro({ apiKey: process.env.KOLABORO_KEY }); # Python k = Kolaboro(api_key=os.environ['KOLABORO_KEY'])

How keys are kept

  • The key is 160 random bits from the server's cryptographic generator, written as kb_live_ plus 40 hex characters.
  • It is shown once. The database stores its SHA-256, the first 4 hex characters (so you can tell keys apart), your label, the country of the request and the creation time. No IP address.
  • Usage is counted per key, per UTC day and per endpoint path with ids removed (for example /api/open/projects/{id}). Nothing else about the calls is stored.
  • You can revoke a key yourself from the usage panel. Revoked keys stop working at once; the usage record stays.
  • Database writes go through functions that only our server can call, so nobody can create keys or spend your quota by calling the database directly.
Protect my purchase