This API provides structured access to traffic congestion data for major cities in Germany, leveraging real-time and historical insights. The API enables developers to extract the list of all tracked German cities and fetch detailed traffic data for any city by name. This includes average congestion levels, time lost in traffic, peak traffic periods, and more. It is ideal for applications in urban planning, logistics, travel advisories, and data analytics platforms. The API is designed with flexibility in mind, supporting simple parameter-based queries to tailor the data output per city.
{
"cities_found": [
{
"rank": 1,
"city": "Berlin"
},
{
"rank": 2,
"city": "Frankfurt am Main"
},
{
"rank": 3,
"city": "Leipzig"
},
{
"rank": 4,
"city": "Hamburg"
},
{
"rank": 5,
"city": "Munich"
},
{
"rank": 6,
"city": "Dusseldorf"
},
{
"rank": 7,
"city": "Nuremberg"
},
{
"rank": 8,
"city": "Stuttgart"
},
{
"rank": 9,
"city": "Dresden"
}
],
"total_cities_found": 9
}
curl --location --request POST 'https://zylalabs.com/api/8212/germany+traffic+data+fetcher+api/14057/get+german+cities' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{
"city_name": "Berlin",
"average_travel_time_per_10_km": 29,
"unit": "min"
}
curl --location --request POST 'https://zylalabs.com/api/8212/germany+traffic+data+fetcher+api/14062/get+average+travel+time+per+10+km+by+city' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
{
"city": "Berlin",
"change": 19,
"unit": "s"
}
curl --location --request POST 'https://zylalabs.com/api/8212/germany+traffic+data+fetcher+api/14068/get+traffic+change+by+city' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
{
"city": "Berlin",
"time_in_rush_hour_per_year": 84
}
curl --location --request POST 'https://zylalabs.com/api/8212/germany+traffic+data+fetcher+api/14074/get+time+in+rush+hour+per+year+by+city' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"city":"Required"}'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Germany Traffic Data Fetcher API provides data on average congestion levels, time lost in traffic, peak traffic periods, and more for major cities in Germany.
The API returns traffic data in a structured format, typically JSON, which allows for easy integration and manipulation of the data.
The API can be used for urban planning, logistics optimization, travel advisories, and data analytics platforms to enhance decision-making related to traffic management.
Developers can tailor the data output by using simple parameter-based queries to specify the city name and the type of traffic data they wish to retrieve.
The traffic data includes fields such as city name, average congestion level, estimated time lost in traffic, and peak traffic periods, allowing for detailed analysis.
This endpoint returns the average travel time required to cover 10 kilometers in a specified German city. The response includes the city name, average travel time in minutes, and the unit of measurement.
This endpoint provides data on the increase or decrease in traffic time for a specified city. The response includes the city name, the change in traffic time in seconds, and the unit of measurement.
The response is structured in JSON format, containing the city name and the total time spent in rush hour per year, expressed in hours. This allows for easy parsing and analysis of rush hour data.
Each endpoint requires the name of a German city as a parameter. Users can obtain a list of available cities from the "get german cities" endpoint to ensure valid input.
The response includes fields such as "rank" (indicating the city's rank based on traffic data) and "city" (the name of the city). This helps users identify and select cities for further traffic data queries.
If no data is available, the API may return an empty result or a specific message indicating the lack of data. Users should implement error handling to manage such scenarios gracefully in their applications.
The API allows users to analyze various traffic data types, including average travel times, traffic changes, and rush hour durations, providing insights into congestion patterns and traffic flow in German cities.
Urban planners can use the traffic data to identify congestion hotspots, assess the impact of infrastructure changes, and optimize traffic management strategies, ultimately improving urban mobility and reducing travel times.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
8,643ms
Service Level:
100%
Response Time:
5,716ms
Service Level:
100%
Response Time:
7,802ms
Service Level:
100%
Response Time:
20ms
Service Level:
100%
Response Time:
1,575ms
Service Level:
100%
Response Time:
718ms
Service Level:
100%
Response Time:
894ms
Service Level:
100%
Response Time:
1,184ms
Service Level:
100%
Response Time:
30ms