US Tornados Data API

API ID 10277

This API provides access to a comprehensive dataset of historical US tornado outbreaks. It offers developers a programmatic way to retrieve structured information about tornado events, including dates, affected states, and the number of tornadoes per outbreak, enabling powerful weather analysis and reporting applications.

100% uptime 1,017 ms avg response

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.

API Documentation

Endpoints

Request
This endpoint allows users to retrieve a list of dates when tornados have occurred in the United States.
Endpoint ID: 19797
POST https://pr213-testing.zylalabs.com/api/10277/us+tornados+data+api/19797/get+tornados+dates
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

This endpoint does not require any input parameters.

API EXAMPLE RESPONSE
JSON
{
    "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"
    ]
}
Get tornados dates — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/10277/us+tornados+data+api/19797/get+tornados+dates' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{}'

Request
This endpoint enables users to retrieve tornado outbreak data for a specific date. By providing a date parameter in the request, developers can filter the dataset to focus on tornado outbreaks that occurred on that particular day.
Endpoint ID: 19798
POST https://pr213-testing.zylalabs.com/api/10277/us+tornados+data+api/19798/get+tornado+data+by+date
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

date
API EXAMPLE RESPONSE
JSON
{
    "tornado_data": [
        {
            "Category": 3,
            "Date": "2008-03-01",
            "Tornados": 20
        }
    ]
}
Get tornado data by date — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/10277/us+tornados+data+api/19798/get+tornado+data+by+date' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"date":"Required"}'

Request
This endpoint provides users with the US states affected by tornadoes filtered by date. To use it, you must indicate a date as a parameter. You can get them from the first endpoint.
Endpoint ID: 19799
POST https://pr213-testing.zylalabs.com/api/10277/us+tornados+data+api/19799/get+affected+states
INPUT PARAMETERS

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

date
API EXAMPLE RESPONSE
JSON
{
    "Date": "2008-03-01",
    "States_Affected": [
        "AL",
        "GA",
        "MS",
        "NC",
        "SC"
    ]
}
Get affected states — CODE SNIPPETS

curl --location --request POST 'https://zylalabs.com/api/10277/us+tornados+data+api/19799/get+affected+states' --header 'Authorization: Bearer YOUR_API_KEY' --header 'Content-Type: application/json' --data-raw '{"date":"Required"}'

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the US Tornados Data API simply include your bearer token in the Authorization header.

Headers
Header Description
Authorization Required Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

(Save 2 months with annual billing 🎉)

🚀 Enterprise Plan
Custom Volume

  • Custom Rate Limit
  • Team & Access Management
  • SLA-backed Uptime
  • Specialized Customer Support
  • Real-Time API Monitoring
  • Enterprise Security & Compliance
Minimum annual contract: USD 10,000

Trusted by leading companies

US Tornados Data API FAQs

The US Tornados Data 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 on which tornadoes occurred in the United States. The response includes a JSON object containing an array of date strings formatted as "YYYY-MM-DD".

Users can filter tornado data by providing a specific date as a parameter in their request. The endpoint will return outbreak data, including the category, date, and total number of tornadoes for that day.

The "get affected states" endpoint returns a list of US states impacted by tornadoes on a specified date. The response includes the date and an array of affected state abbreviations.

Each endpoint returns data in a structured JSON format. For example, the "get tornado data by date" endpoint returns a JSON object with a "tornado_data" array, where each object contains fields like "Category", "Date", and "Tornados".

The "get affected states" endpoint requires a date parameter to filter the results. Users can obtain valid dates from the "get tornados dates" endpoint to ensure accurate requests.

Typical use cases include analyzing tornado patterns over time, creating visualizations of tornado outbreaks, and generating reports for educational or research purposes. Developers can integrate this data into weather applications or disaster preparedness tools.

If no tornado data is available for a specific date, the API will return an empty array in the response. Users should implement checks in their applications to handle such cases gracefully, ensuring that their applications can manage empty results without errors.

The key fields in the response data for tornado outbreaks include "Category" (classification of the outbreak), "Date" (the outbreak's start date), "Tornados" (total number of tornadoes), and "States Affected" (list of affected states).

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs