Talertbyid: Queries active and upcoming times for a particular alert.
In MBTAr: Access Data from the Massachusetts Bay Transit Authority (MBTA) Web API

Description Usage Arguments Value See Also

Returns all information about a given alert. Some fields may be empty for an alert.

1	Talertbyid(alert_id)

alert_id

Unique identifier for the alert. Example: "781"

`alert_id`	The unique identifier for the alert
`effect_name`	The human-readable name for the effect. Example: "Shuttle bus"
`effect`	The GTFS-realtime-compatible code for the effect. Example: "DETOUR"
`cause`	The human-readable name for the cause. Sometimes empty. Example: "maintenance"
`header_text`	A brief summary of the situation (GTFS-realtime-compatible). Example: "Shuttle buses replacing Red Line service from Sat Jun 01, 2013 to Sun Jun 30, 2013 every Saturday and Sunday from 09:00 PM to end of service due to tie replacement"
`short_header_text`	A shortened version of header_text. Example: "Shuttle buses replacing Red Line service from Sat Apr 27 to Sun May 26 every Saturday and Sunday due to maintenance"
`description_text`	Additional details (GTFS-realtime-compatible). Example: "Affected stops: Alewife Station Davis Station Porter Square Station Harvard Square Station"
`severity`	Possible values: "Severe", "Moderate", "Minor"
`created_dt`	Date and time the alert was created, in epoch time. Example: "1361395938"
`last_modified_dt`	Date and time the alert was last modified, in epoch time. Example: "1361395938"
`service_effect_text`	Summarizes the service and the impact to that service. Example: "Minor Route 1 delay"
`timeframe_text`	Summarizes when an alert is in effect. Example: "starting Saturday"
`alert_lifecycle`	Identifies whether alert is a new or old, in effect or upcoming. Not intended to be human-readable. Possible values: "Upcoming", "New", "Ongoing", "Ongoing-Upcoming." See notes.
`effect_start`	Date and time of the start of the effect period, in epoch time. Example: "1367110800"
`effect_end`	Date and time of the end of the effect period, in epoch time. Can be empty if effect end is not known. Example: "1367130600"
`affected_route_type`	GTFS-compatible code for route type (i.e. mode). Appears for service alerts only (not access alerts). Example: "1"
`affected_mode_name`	Human-readable name for the mode. Example: "Subway"
`affected_route_id`	The unique GTFS-compatible identifier for the route. Example: "Red"
`affected_route_name`	The human-readable name for the route. Example: "Red Line"
`affected_direction_id`	The GTFS-compatible identifier for the direction. Example: "0"
`affected_direction_name`	Human-readable direction name. Example: "Westbound"
`affected_trip_id`	The GTFS-compatible unique identifier for the trip. Example: "CR-Newburyport-CR-Weekday-129"
`affected_trip_name`	Human-readable trip name. Example: "129 (5:00 pm from North Station)"
`affected_stop_id`	The GTFS-compatible unique identifier for the stop. Example: "70061"
`affected_stop_name`	The GTFS-compatible name for the stop (not unique). Example: "Alewife Station Red Line"
`affected_route_hide`	Whether this route should be hidden from users. See notes. Possible values: "true". Only included if "true."
`affected_elev_id`	Unique identifier for the elevator/escalator. Example: "926"
`affected_elev_name`	Human-readable name for the elevator/escalator. Example: "SOUTH STATION - Lobby to Street"
`affected_elev_type`	Type of the elevator/escalator. Possible values: "Elevator", "Escalator", "Lift"
`affected_elev_stop_id`	The GTFS-compatible unique identifier for the stop. Example: "70080"
`affected_elev_stop_name`	The GTFS-compatible name for the stop (not unique). Example: "South Station - Inbound"
`affected_elev_stop_parent_id`	The GTFS-compatible unique identifier for the larger station associated with the stop, if one exists. Can be empty if parent station does not exist. Example: "place_sstat"