API Overview

The Geo Nearby API returns the nearest known place for a given geographic coordinate. It is useful when you already have a lat/lon pair and want to resolve it into a human-readable place with metadata.

The Geo Search API returns place matches for a free-text query. Each result includes name, coordinates , timezone, and country/continent metadata. Ideal for using in combination with our weather and mobility endpoints.

The Weather Forecast API provides comprehensive weather data for locations globally: Current Weather Data: Immediate insights into the current weather conditions. 2-Hour Minutely Precipitation Forecast: Minute-by-minute precipitation data for precise forecasting of rainfall and snowfall. 7-Day Hourly Forecast: Detailed hourly weather predictions for the upcoming week. 7-Day Daypartly Forecast: Detailed daypartly weather predictions for the upcoming week. 15-Day Daily Forecast: Extended daily weather forecasts for the next 15 days. With the default values , the forecast costs 1 credit. For longer periods, it costs 3 credits.

Retrieve radar-based precipitation nowcasts in 5-minute steps, including precipitation type, intensity, probability, and ready-to-use image frames per timestep.

The Weather Climate API offers monthly climate data for locations worldwide, providing insights into average temperatures, precipitation trends, and long-term climate patterns. The climate averages are based on weather observations from the past ten years. This approach is chosen to provide a globally accurate representation of the expected weather in the current climate for each month. The 10-year climate average is updated annually, ensuring the data remains relevant and accurate.

The outstanding weather warnings.

List of available weather models and elements. When latitude and longitude are provided, only models available for that location are returned.

Get location timeseries for provided model and elements.

Get a weather forecast along a route, where for each waypoint the correct forecast offset is chosen based on the estimated arrival time at that point. You provide a series of coordinates and a speed; the API calculates when you'll arrive at each point and returns the weather values for the requested elements at the matching forecast offsets. This gives you a time-dependent forecast per location instead of a static forecast for a single moment, which is useful for route planning, navigation, and logistics where weather conditions change along the way. Available for all [weather models] except ensemble models. Credits = waypoints count x elements count

List of available weather ensemble models and elements. When latitude and longitude are provided, only models available for that location are returned.

Retrieve an ensemble forecast timeseries for a single location, including individual ensemble members and aggregate statistics for each requested element and level.

List of available weather models and elements. When latitude and longitude are provided, only models available for that location are returned.

Get location timeseries for provided model and elements.

Get a weather forecast along a route, where for each waypoint the correct forecast offset is chosen based on the estimated arrival time at that point. You provide a series of coordinates and a speed; the API calculates when you'll arrive at each point and returns the weather values for the requested elements at the matching forecast offsets. This gives you a time-dependent forecast per location instead of a static forecast for a single moment, which is useful for route planning, navigation, and logistics where weather conditions change along the way. Available for all [weather models] except ensemble models. Credits = waypoints count x elements count

List of available weather ensemble models and elements. When latitude and longitude are provided, only models available for that location are returned.

Retrieve an ensemble forecast timeseries for a single location, including individual ensemble members and aggregate statistics for each requested element and level.

Returns a list of seaports worldwide, roughly 3,700 in total. Each port can be filtered by harbor size. Source: Data is based on the [NGA World Port Index ], the official reference publication maintained by the U.S. National Geospatial-Intelligence Agency. The WPI catalogs the locations and physical characteristics of major ports, harbors, and terminals around the world, and is the most widely used authoritative dataset for global port information. Size distribution: | Size | Approx. count | Description | |------|--------------|-------------| | `large` | ~170 | Major deep-water ports handling large vessels | | `medium` | ~360 | Mid-sized commercial ports | | `small` | ~1,000 | Smaller harbors with limited facilities | | `very_small` | ~2,100 | Minor ports, anchorages, and landing sites | Filtering: Pass the `size` query parameter to filter by one of the values above . Omit it to return all ports.

Returns the full record for a single port, identified by its WPI ID. The response includes the port's identity and location along with its classification . It also contains nested objects describing the port's physical and operational characteristics: depths, maximum vessel dimensions, entrance restrictions, pilotage, tugs, quarantine, communications, facilities, cranes, services, supplies, repair capabilities, and other port features.

The Traffic Overview API provides a real-time snapshot of traffic conditions on Dutch roads. It includes congestion reports, road closures, and traffic measures, aggregated into a single feed. The API is updated every few minutes and designed for building traffic dashboards, travel apps, and mobility solutions.

The Traffic GeoJSON API provides real-time traffic events for the Netherlands in GeoJSON format. Each feature represents a road closure, congestion, or traffic measure with full geometry for visualization on maps. This makes it ideal for interactive applications, dashboards, and GIS integrations.

Planner location search, used to get start and destination location.

The Planner Mixer plans a trip between two locations and streams multiple travel options in real time. Where a normal trip planner returns one answer, the mixer keeps re-planning the same journey under different assumptions — for example by allowing a bicycle for the first mile, or by permitting shared mobility — and pushes every result to the client as soon as it is ready. Each result carries a `grade` so the client can rank alternatives, and a `modifiers` list explaining how that result differs from the default plan request. Because results arrive progressively, this is a WebSocket endpoint, not a REST endpoint. Messages in both directions are binary Protocol Buffers , not JSON. The server closes the connection when the mixer has no further results.

List of available transit near a specified location, based on latitude and longitude coordinates. If there are more then 3 routes closer within 1000m routes within 1000m will be returned, if there are less then 3 outes all routes within 5000m will be returned

This endpoints returns public transport trips departing from a certain stopplace for the next hour.