SKYDB

SKYDB Building database

Tall buildings worldwide, with heights, construction status and the companies involved.

Rankings of tall buildings

Tall Building Markets

  • Global building statistics
  • Biggest cities worldwide
  • Country market overviews
  • Construction activity
  • Annual completions
Speaker at a lectern in front of a skyscraper presentation

SKYDB Awards

The community is honoring the best new skyscrapers. A legacy since 1999.

View award winners

SKYDB Membership

Create a free account, choose Premium or apply to contribute as a volunteering Editor.

Choose your access

SKYDB Community

SKYDB Editors visiting a skyscraper construction site

Join for free

Become a volunteering Editor optionally or get Editor rights with Premium.

Compare memberships

SKYDB Products

Professional building research, data exports and API access, plus advertising offerings.

Research & data

Consulting & advertising

SKYDB Insights charts showing buildings by decade, status, use, floor count and height

SKYDB Insights

Professional research into buildings and participating companies.

View Insights plans

Tall buildings, tracked.

SKYDB is collecting verifiable information about buildings.

About SKYDB

Using SKYDB

Chongqing skyline beside the river

Who we are

SKYDB is the source for tall building information worldwide.

About SKYDB

Interactive building map

Explore all projects on an interactive map anywhere on earth.

Free map access

Upgrade your map experience

SKYDB map with building pins and a building record in Lower Manhattan

Join SKYDB

The map is for registered members. Create a free account to explore.

Create a free account
document

What format do API responses have?

Every response is a JSON object with the fields ok, data and meta; timestamps follow RFC 3339 in UTC, and heights are in meters.

Every response is a JSON object. A successful one has ok set to true, the records under data and request details under meta. The SKYDB API page shows a complete example response for one building.

Timestamps follow RFC 3339 in UTC, for example 2026-08-03T07:05:24Z. Dates of a building can be partial, such as 2010 or 2010-01, because a completion year is often what the sources state. Field names carry their unit, so height_m is a height in meters.

Each response also carries a notice field with the license terms. New fields can appear within version 1 at any time, so a client should ignore properties it does not know. The API reference lists the fields of each endpoint.