CitySDK API

Free to Use Varies (check documentation)

Overview

CitySDK provides open APIs for a selection of European cities, offering access to urban data such as public services, demographics, and points of interest. It is designed to help developers build city-aware applications that work across multiple European municipalities. The API is free to use and follows open data principles.

Beginner Tip

CitySDK data availability varies by city, so check the documentation for which endpoints are supported in your target city before building. Start with a city that has the most complete dataset for the smoothest development experience.

Available Data

CitySDK data via REST API

Example Response

JSON Response
{
  "status": "success",
  "data": {
    "result": "Data from CitySDK",
    "description": "Open APIs for select European cities",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

id Unique identifier for the data layer or object within the CitySDK system.
name Human-readable name describing the layer or city feature.
geometry GeoJSON geometry object describing the shape or location of the feature.
properties Key-value pairs containing metadata specific to the city feature, such as opening hours or contact info.
updated_at ISO 8601 timestamp of the last update for this data record.

Implementation Example

Request
const url = "http://www.citysdk.eu/citysdk-toolkit/";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

404 Not Found for a city endpoint Not all cities implement the same set of CitySDK endpoints.
Check the CitySDK documentation for the specific city to see which layers and endpoints are available.
Slow response times Some city APIs are hosted on public infrastructure with limited resources.
Cache responses locally and avoid making repeated identical requests. Implement a timeout of at least 10 seconds.
Unexpected data format Different city implementations may return slightly different JSON structures.
Always validate the response structure before parsing and handle optional fields gracefully with default values.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Geocoding
Difficulty Beginner
Verified: 2026-04-07

Related Tags

Similar APIs

View All →