including relationships in Shape data not working?

[Brian Runck]

It seems to me that I was able to use "include=route" in the query string when doing a GET on the Shapes endpoint, but when I do this now there is no relationships node returned.

For example:

curl -X GET "https://api-v3.mbta.com/shapes?filter%5Broute%5D=Red%2CMattapan%2COrange%2CGreen-B%2CGreen-C%2CGreen-D%2CGreen-E%2CBlue%2CCR-Fairmount%2CCR-Fitchburg%2CCR-Worcester%2CCR-Franklin%2CCR-Greenbush%2CCR-Haverhill%2CCR-Kingston%2CCR-Lowell%2CCR-Middleborough%2CCR-Needham%2CCR-Newburyport%2CCR-Providence%2CCR-Foxboro%2CBoat-F4%2CBoat-F1%2CBoat-EastBoston%2CBoat-Lynn%2CBoat-F6%26include%3Droute" -H "accept: application/vnd.api+json" -H "x-api-key: <insert API key>"

[Developer at MBTA]

Hi Brian, thanks for reaching out.

This is something we removed from the V3 API on 2020-05-01. In that update, we made a few modifications to our API, specifically: 

• `name`, `direction_id`, and `priority` were removed from attributes
• `route` and `stops` were removed from relationships

You can find this information in our changelog. 

As a result of this update, when you use the "include=route" query in your API call, you will no longer receive a relationships node in the response, as was previously the case. The use cases covered by these fields should be accommodated by /route_patterns endpoint in the V3 API, which provides comprehensive route and stop data.

We understand that changes like these can require adjustments in how the API is used, and we are here to help! If you have any further questions, please don't hesitate to reach out.

All the best,

Developer@MBTA

[Brian Runck]

I'm having trouble understanding how route patterns gets to shapes of the various routes. Is there more informatin about how the shapes can be obtained that way?