TSA Wait Times TSA WAIT TIMES

TSA Wait Times API


Documentation

Information for interacting with the TSAWaitTimes.com API can be found below. The Request URLs have variables as part of the URL. The possible variables are below. Responses can be returned in both JSON and XML formats. The data elements can be referenced via the Data Dictionary.

Table of Contents

Variables

These are the potential variables that you will need to pass to the API Request URL.

  • {APIKEY} : Your API Key
  • {FORMAT} : Either json or xml (Default is json if not specified)
  • {CODE} : A 3-character airport code (Example: ATL for Atlanta)

All data can be retrieved via GET calls placed to a specific URL as detailed below.

To record a time, you'll need to POST your request to the specific URL as detailed below.

You are encouraged to cache the results locally for optimal and efficient performance.

GET LIST OF AIRPORTS

Retrieve a list of currently supported airports.

REQUEST GET

RESPONSE

JSON Response

XML Response

GET SPECIFIC AIRPORT STATUS

Retrieve the current estimated wait time, precheck lanes, and airport conditions for a specific airport.

Airport codes can be retrieved from the GET LIST OF AIRPORTS call. The airport code value should replace the {CODE} variable below.

REQUEST GET

RESPONSE

JSON Response using {CODE} of ATL

XML Response

SUBMIT USER WAIT TIME

If you plan to allow your end users to submit their wait time experiences for others to know about, you can send those user reports to us. This request will require you to POST to the URL below with the appropriate variables.

REQUEST POST

POST Variable Description
code [STRING] The 3 character airport code. Example: code=ATL for Atlanta Hartsfield-Jackson

FOR TESTING PURPOSES, please use the airport code of XXX
user_reported [INTEGER] The user's reported wait time in minutes.

Valid options for user_reported values are below.

5
10
15
20
25
30
35
40
45
50
55
60
75
90
105
120
135
150
165
180
195
210
225
240

RESPONSE

JSON Response

XML Response

Data Dictionary

Below are the individual data elements and what they mean.

Data Element Description
average [STRING] The average ground delay time at this airport right now
city [STRING] The city where the airport is located
code [STRING] A 3-character IATA airport code
end_time [STRING] The anticipated end time for an FAA-issued ground stop
latitude [STRING] The airport's geographic latitude
longitude [STRING] The airport's geographic longitude
name [STRING] The name of the airport. If referenced from within the precheck_checkpoints node/array, 'name' may reference either the airport terminal name or the name of the terminal checkpoint.
precheck [INTEGER] TSA PreCheck indicator. If PreCheck is available, this will be set to 1. Otherwise it will be 0
reason [STRING] The reason for a delay or stop. This field is used within the FAA Alerts for ground stops, ground delays, and general delays
rightnow [INTEGER] The estimated wait time at the airport at this time rounded to nearest integer of minutes. Wait times are estimates, subject to change, and may not be indicative of a traveler's experience.
rightnow_description [STRING] A consumer-friendly description of the current estimated wait time
state [STRING] The state where the airport is located
success [BOOLEAN] Whether or not the request was successful.
timeslot [STRING] The hour for a particular wait time estimate. Format will be beginning hour to end hour. Example: 5 am - 6 am
trend [STRING] The current trend for departure delays at this airport right now
user_reported [INTEGER] Number of wait time minutes being reported by users currently at the airport. A value of zero indicates that we do not currently have user-submitted reports for this airport at this time
utc [INTEGER] The UTC (Coordinated Universal Time) offset for this airport. Useful for determining current time at the airport.
waittime [DECIMAL] The estimated wait time for a given timeslot. For example, 10.5 would be 10 minutes and 30 seconds. 10.2 would be 10 minutes and 12 seconds.

Error Responses

Below are a list of potential error codes you might receive and what they mean.

Error Message Description
No API Key Provided You need to pass along your API key for each request. This error will also get triggered if an invalid API key is sent.
This account has not been verified yet You need to verify your email address before an API call can be made. When you created your account, we sent you an email with an authorization link in it. You will need to click that link. You can have another email sent to you from the My Account screen. Just click the grey Unverified Account icon at the top of the page. Please check your Junk or Spam folder if you don't see it within a few seconds.
This API key is not active We may disable API keys for several reasons including a violation of our terms and conditions or high/abusive usage. Please email us at [email protected] to have your API key reinstated.
This API key does not have an active subscription All API calls require a paid subscription. You can purchase a subscription from the My Account page.
This API key expired on DATE Your API subscription has expired. All API calls require a paid subscription. You can extend your subscription from the My Account page.
Invalid Airport Code Please pass along a valid 3-character airport code.
No airport code provided When submitting a user-reported time, please POST the variable "code" with a valid 3-character IATA code
Invalid Number of Minutes The number of minutes submitted was not a valid number. Refer to the documentation for valid integers.
Wait Time Not Submitted When submitting a user-reported time, please POST the variable "user_reported" with a valid integer of minutes
Could not save There was an unknown error on our side and we could not save the posted data.

Frequently Asked Questions

API Questions





Billing Questions





API Pricing

Pricing is based upon monthly subscription pricing.


Months Discount Total Cost  
1 $14.95
3 $44.85
6 10% Off $89.70
$80.73
Save $8.97!
12 15% Off $179.40
$152.49
Save $26.91!