Changelog

Get Help with MBTA Data

To connect with developers and members of our team, visit our Google Group.

MBTA Developers Google Group

2021年01月09日

This version coincides with a major change to stop IDs for Commuter Rail stops and Nubian (formerly Dudley) station. For backward compatibility, versions before this one treat all requests that specify an "old" stop ID like they had also specified the corresponding "new" stop ID(s). This version removes that translation. (After January 9, 2021, stop IDs in responses are always the "new" ones in all V3 API versions.)

This version also includes the following minor changes:

• The /predictions endpoint now correctly returns an error if a date filter is specified; previously, it would accept one but not do anything with it.
• The /shapes endpoint no longer accepts direction_id as a filter or a sort key; these were mistakenly not removed in version 2020年05月01日 when the corresponding attribute was removed from /shapes.

2020年05月01日

The version removes several fields from the /shapes endpoint.

• name, direction_id, and priority have been removed from attributes.
• route and stops have been removed from relationships.

The use cases for these fields are accommodated by the /route_patterns endpoint.

2019年07月01日

This version introduces cleanups to make the V3 API more consistent.

• The /schedules endpoint no longer returns a 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 endpoint.
• The use of underscores (_) has been made consistent throughout the V3 API.
  • /route-patterns was renamed to /route_patterns.
  • /live-facilities 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 endpoint.

For security purposes, we have disabled TLS 1.0/1.1 access to the V3 API. As of July 1, 2019, TLS 1.2 is the minimum supported version.

2019年04月05日

This version introduces strict validation of parameters passed as a filter and/or include. The V3 API will return HTTP 400 if the caller passes an unsupported value. Lists of supported values for filters and includes are in the V3 API Documentation.

2019年02月12日

The stop_id field for the /predictions endpoint can now change in some additional cases:

• Red Line: Alewife, Braintree
• Orange Line: Forest Hills, Oak Grove
• Green Line: Kenmore, Park Street

2018年07月23日

The stop_id field for the /predictions endpoint can now change in some cases where we know that the vehicle will stop at a different stop. In particular, we use this for the Commuter Rail: Back Bay, South Station, and North Station for track assignments.

Since track assignments are now reflected in the stop_id field, the track field is removed.

2018年05月07日

The last_updated field on the /vehicles endpoint was replaced by updated_at to more closely match the names used by /alerts.

2017年11月28日

Initial public release

Developers

Learn more

Use of MBTA data is governed by the MassDOT Developers License Agreement (PDF, 85.5 KB).