Upcoming API changes: 2019-07-01

[Developer at MBTA]

Hello developers,

We wanted to let you know about some upcoming changes to the V3 API, to be made as a part of a new version 2019-07-01.

This version introduces cleanups to make the API more consistent.

• The Schedules API no longer returns an departure time if it’s not possible to board, or an arrival time if it’s not possible to alight at a stop
  • This brings it into line with the Predictions API
• The use of underscores (_) has been made consistent throughout the API
  • /route-patterns/ was renamed to /route_patterns/
  • /live-facilties/ was renamed to /live_facilities/ and the type of those results is now `live_facility`
• Facilities now have a `short_name` and `long_name` field: the `name` field was removed
  • This brings it into line with the Routes API

For security purposes, we will also disable TLS 1.0/1.1 access to the API, starting 2019-07-01.

This version is available for use starting today, and will become the default for new keys and anonymous access on 2019-07-01.

If you have any questions or comments about the new version, please let us know!

Sincerely,

Developer@MBTA

[Developer at MBTA]

This change to the TLS protocol will also affect the GTFS-Realtime files hosted under cdn.mbta.com. We encourage all developers to update their systems to support TLS 1.2.

Sincerely,

Developer@MBTA

[Grace Vincens]

Hello! 

I was wondering if there was public access to your historical ridership data 2007 to present? I seem to be only able to access 2016-2018 

Thank you!

On Tuesday, June 11, 2019 at 2:40:27 PM UTC-4, Developer at MBTA wrote:

[Developer at MBTA]

 Hi Grace,

This is a great question for our friends in the MBTA Office of Performance Management and Innovation! You can reach them at perfo...@mbta.com

Thanks,

Developer@MBTA

[Developer at MBTA]

These changes have been rolled out.

Sincerely,

Developer@MBTA

On Tuesday, June 11, 2019 at 2:40:27 PM UTC-4, Developer at MBTA wrote: