Updates
All updates will be provided here as well as on our news feed.
api_key support is here, account/key freeze coming - December 4, 2014
HTTP Support Available - November 10, 2014
Beta Sunset Notice
With the transition to our production portal complete, we plan to shut down this beta site, effective Friday, February 27, 2015. Any applications making calls to https://wmataapibeta.azure-api.net will need to be redirected to our production environment.
Beta Announcement
Welcome, WMATA API users! We want to make you aware that we are planning for a transition to a new API service provider. Our target timeframe is Monday, December 15th. To ensure a seamless transition, we request that you complete the two steps below by Monday, December 8th, at the latest.
Step 1 - Modify Existing API URLs and Publish
You will need to modify your applications to include your API key twice, as shown below, and publish them to the relevant app stores or other repositories. For example:
http://api.wmata.com/StationPrediction.svc/GetPrediction/B03?api_key=YOUR_API_KEY
will become:
http://api.wmata.com/StationPrediction.svc/GetPrediction/B03?api_key=YOUR_API_KEY&subscription-key=YOUR_API_KEY
See update regarding api_key now being available. Be sure you are passing in the api_key parameter name in all lower-case!
Step 2 - Test Modified URLs in Beta Site
We also strongly encourage you to test your applications with the beta site using the URLs shown below. All keys and accounts created in our existing developer portal prior to 9 AM on November 6, 2014 have been migrated to this beta site.
If you signed up or added a key after this date, please follow the normal signup procedures on this site so that you can test. Note that any new accounts or keys created on this beta site for testing purposes will NOT be migrated as part of the final release. If you need a permanent key, you need to sign up for one on our existing developer portal. We will migrate all accounts and keys in the existing developer portal as we near our final launch date.
In order to test your application functionality, please change your URLs from:
http://api.wmata.com/StationPrediction.svc/GetPrediction/B03?api_key=YOUR_API_KEY
to:
https://wmataapibeta.azure-api.net/StationPrediction.svc/GetPrediction/B03?api_key=YOUR_API_KEY&subscription-key=YOUR_API_KEY
http://wmataapibeta.azure-api.net/StationPrediction.svc/GetPrediction/B03?api_key=YOUR_API_KEY
Note the addition of HTTPS as well as the new subscription-key parameter. The beta site currently only supports HTTPS for API calls, but we do plan to have HTTP support prior to the transition.
See update regarding HTTP support now being available.
See update regarding api_key now being available. Be sure you are passing in the api_key parameter name in all lower-case!
API Documentation
Check out the automatically generated API Documentation that describes how to use the APIs and includes code samples in multiple languages. The API Console allows you to directly interact with the API right here in the developer portal.
Contact Us
We encourage you to contact us at api-support@wmata.com with any questions or concerns.
Be sure to subscribe to our news feed to keep up to date on API-related announcements!