This API exposes data on historical tornado outbreaks in the United States. The API returns structured data representing each tornado outbreak as a JSON object within a list. Each object contains the following fields: 'Category' (integer representing the outbreak's classification), 'Date' (string representing the outbreak's start date), 'Tornados' (integer representing the total number of tornadoes in the outbreak), and 'States Affected' (string representing a comma-separated list of US states affected). The API uses a single endpoint, /tornadoes, to serve this data. Developers can retrieve the complete dataset using a simple GET request to this endpoint. The data is presented in a JSON array of JSON objects, making it easily parsable and integrable into various applications. The API adheres to standard RESTful principles for data access, facilitating seamless integration with various programming languages and frameworks. For example, a developer could use Python's requests library to fetch the data, parse the JSON response, and subsequently perform analysis or integrate the data into their visualization tools. This API provides a readily accessible and structured way to programmatically access and utilize valuable historical weather data.
{
"dates": [
"2016-11-16",
"2016-08-27",
"2016-04-28",
"2016-05-13",
"2016-04-17",
"2016-05-1",
"2016-03-23",
"2015-05-8",
"2015-02-28",
"2015-03-13",
"2015-03-12",
"2015-04-12",
"2015-04-27",
"2014-11-24",
"2014-05-27",
"2014-05-26",
"2014-05-19",
"2014-05-9",
"2013-11-17",
"2013-05-20",
"2013-05-3",
"2013-04-27",
"2013-04-16",
"2013-03-2",
"2012-06-1",
"2012-04-27",
"2012-03-2",
"2012-02-29",
"2012-02-6",
"2011-08-23",
"2011-05-22",
"2011-04-27",
"2011-04-15",
"2011-03-27",
"2011-03-16",
"2010-06-10",
"2010-05-27",
"2010-05-4",
"2010-04-24",
"2010-04-8",
"2010-03-19",
"2009-06-12",
"2009-05-27",
"2009-05-11",
"2009-04-12",
"2009-03-29",
"2009-03-3",
"2008-06-17",
"2008-05-13",
"2008-05-10",
"2008-04-13",
"2008-03-1",
"2008-02-17",
"2008-02-6",
"2007-06-7",
"2007-05-28",
"2007-05-27",
"2007-04-24",
"2007-04-16",
"2007-03-26",
"2006-05-29",
"2006-05-8",
"2006-04-21",
"2006-03-29",
"2005-06-7",
"2005-05-22",
"2005-05-19",
"2005-05-1",
"2005-04-28",
"2005-04-2",
"2005-03-21",
"2004-06-10",
"2004-05-27",
"2004-05-24",
"2004-05-10",
"2004-04-15",
"2004-03-28",
"2004-03-27",
"2003-11-20",
"2003-08-11",
"2003-06-28",
"2003-05-24",
"2003-05-13",
"2003-04-24",
"2003-04-12",
"2003-03-22",
"2002-11-24",
"2002-08-13",
"2002-06-1",
"2002-05-22",
"2002-05-17",
"2002-04-25",
"2002-04-8",
"2002-03-28",
"2001-06-5",
"2001-05-27",
"2001-05-21",
"2001-05-2",
"2001-04-26",
"2001-03-13",
"2000-06-21",
"2000-06-5",
"2000-05-29",
"2000-05-23",
"2000-05-10",
"2000-04-13",
"2000-03-29",
"1999-06-10",
"1999-06-1",
"1999-05-25",
"1999-05-17",
"1999-04-27",
"1999-04-11",
"1999-03-25",
"1999-03-13",
"1998-11-16",
"1998-08-22",
"1998-07-12",
"1998-06-28",
"1998-06-13",
"1998-05-28",
"1998-05-19",
"1998-05-14",
"1998-05-3",
"1998-04-26",
"1998-04-17",
"1998-03-27",
"1998-03-10",
"1997-06-7",
"1997-05-27",
"1997-05-10",
"1997-04-26",
"1997-04-13",
"1997-03-22",
"1996-08-28",
"1996-08-12",
"1996-06-28",
"1996-06-2",
"1996-05-21",
"1996-05-11",
"1996-05-3",
"1996-04-10",
"1996-03-22",
"1995-06-20",
"1995-06-10",
"1995-05-29",
"1995-05-17",
"1995-05-7",
"1995-04-27",
"1995-04-15",
"1995-03-21",
"1994-06-27",
"1994-05-27",
"1994-05-17",
"1994-05-5",
"1994-04-26",
"1994-03-26",
"1994-03-13",
"1993-06-29",
"1993-05-24",
"1993-05-4",
"1993-04-20",
"1993-03-27",
"1992-06-17",
"1992-05-27",
"1992-05-21",
"1992-05-11",
"1992-04-27",
"1992-04-12",
"1992-03-29",
"1992-03-18",
"1991-06-15",
"1991-06-2",
"1991-05-21",
"1991-05-16",
"1991-05-8",
"1991-04-27",
"1991-04-17",
"1991-03-21",
"1990-08-26",
"1990-06-20",
"1990-06-1",
"1990-05-18",
"1990-04-28",
"1990-04-17",
"1990-03-23",
"1989-06-12",
"1989-05-27",
"1989-05-10",
"1989-04-28",
"1989-04-20",
"1989-03-12",
"1988-05-27",
"1988-05-20",
"1988-05-4",
"1988-04-16",
"1988-03-30"
]
}
curl --location --request POST 'https://zylalabs.com/api/10282/us+tornado+database+api/19804/get+tornados+dates' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'
{
"tornado_data": [
{
"Category": 3,
"Date": "2008-03-01",
"Tornados": 20
}
]
}
curl --location --request POST 'https://zylalabs.com/api/10282/us+tornado+database+api/19807/get+tornado+data+by+date' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"date":"Required"}'
{
"Date": "2008-03-01",
"States_Affected": [
"AL",
"GA",
"MS",
"NC",
"SC"
]
}
curl --location --request POST 'https://zylalabs.com/api/10282/us+tornado+database+api/19811/get+affected+states' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"date":"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 US Tornado Database API provides access to a comprehensive dataset of historical tornado outbreaks in the United States, including details such as outbreak dates, affected states, and the number of tornadoes per outbreak.
The API returns data in a structured JSON format, specifically as a JSON array containing JSON objects for each tornado outbreak.
Each JSON object returned by the API includes the following fields: 'Category' (integer), 'Date' (string), 'Tornados' (integer), and 'States Affected' (string).
Developers can use the API to retrieve historical tornado data for analysis, reporting, or visualization purposes. For example, they can fetch the data using a GET request, parse the JSON response, and integrate it into weather analysis tools or applications.
The API provides a readily accessible and structured way to access valuable historical weather data, enabling developers to create powerful weather analysis and reporting applications that can enhance understanding of tornado patterns and impacts.
The "get tornados dates" endpoint returns a list of dates when tornadoes occurred in the United States. The response includes a JSON object with a "dates" field, which is an array of strings representing each date.
Users can filter tornado data by providing a specific date as a parameter in their request. The endpoint will return outbreak data for tornadoes that occurred on that date, including details like category and total tornadoes.
The "get affected states" endpoint provides a list of US states impacted by tornadoes on a specified date. The response includes the date and an array of affected states, allowing users to understand regional impacts.
Each endpoint returns data in a structured JSON format. For example, the "get tornado data by date" endpoint returns a JSON object containing a "tornado_data" array, where each object includes fields like "Category," "Date," and "Tornados."
The "get affected states" endpoint requires a date parameter to filter the results. Users must specify a valid date to retrieve the corresponding states affected by tornadoes on that day.
Typical use cases include weather analysis, safety planning, and educational purposes. Developers can use the data to visualize tornado patterns, assess risks in specific regions, or create alerts for affected areas.
If no tornado data is available for a specified date, the API will return an empty array in the response. Users should implement checks in their applications to handle such scenarios gracefully, ensuring they provide appropriate feedback to users.
The "Category" field indicates the classification of the tornado outbreak based on its intensity, typically following the Enhanced Fujita Scale. This information helps users assess the severity and potential impact of the tornadoes associated with that outbreak.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
Service Level:
100%
Response Time:
18ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
1,921ms
Service Level:
100%
Response Time:
14,597ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
181ms
Service Level:
100%
Response Time:
200ms
Service Level:
100%
Response Time:
304ms
Service Level:
100%
Response Time:
149ms
Service Level:
100%
Response Time:
7,076ms
Service Level:
100%
Response Time:
1,971ms
Service Level:
100%
Response Time:
1,855ms
Service Level:
100%
Response Time:
1,076ms
Service Level:
100%
Response Time:
4,649ms
Service Level:
100%
Response Time:
650ms
Service Level:
100%
Response Time:
2,450ms
Service Level:
100%
Response Time:
1,608ms
Service Level:
100%
Response Time:
3,168ms
Service Level:
100%
Response Time:
8,179ms
Service Level:
100%
Response Time:
1,942ms