[{"data":1,"prerenderedAt":262},["ShallowReactive",2],{"docs-\u002Fdocs\u002Frest-api\u002Fdepartures":3,"_apollo:default":258,"_apollo:stationEditor":259,"_apollo:feedManagement":260,"_apollo:transferAnalyst":261},{"id":4,"title":5,"body":6,"description":247,"extension":248,"meta":249,"navigation":252,"path":253,"seo":254,"stem":255,"__hash__":256,"lastUpdated":257},"content\u002Fdocs\u002Frest-api\u002Fdepartures.md","REST API - Stop departures",{"type":7,"value":8,"toc":236},"minimark",[9,14,18,32,37,45,52,56,72,75,104,122,146,150,157,180,191,200,204,227,230],[10,11,13],"h2",{"id":12},"stop-departures","Stop departures",[15,16,17],"p",{},"The stop-departures endpoint provides information about when transit trips serve a given stop.",[15,19,20,21,26,27,31],{},"To instead see departures for a specific transit trip, use the ",[22,23,25],"a",{"href":24},"\u002Fdocumentation\u002Frest-api\u002Ftrips","trips endpoint",". For an overview of trips and schedules, see the ",[22,28,30],{"href":29},"\u002Fdocumentation\u002Fconcepts\u002Ftrips-schedules","Trips and schedules concept page",".",[33,34,36],"h3",{"id":35},"departures-or-transit-routing","Departures or transit routing?",[15,38,39,40,44],{},"Use ",[41,42,43],"strong",{},"stop departures"," for a known stop. It returns the trips serving that stop in a time window, in departure order, with real-time arrival estimates where a feed provides them. It does not plan routes, transfers, or walking.",[15,46,39,47,51],{},[22,48,50],{"href":49},"\u002Fdocumentation\u002Frouting-platform\u002Ftransit-otp","transit routing"," for an origin and a destination. It selects stops, routes, and transfers, and returns itineraries with walking legs, timings, and geometry.",[33,53,55],{"id":54},"how-do-i-specify-a-date","How do I specify a date?",[15,57,58,59,63,64,67,68,71],{},"By default, departures for the next hour (in the local timezone for the stop) are shown. You can increase this time window using the ",[60,61,62],"code",{},"next"," parameter. You can also specify the start and end times manually, using the ",[60,65,66],{},"start_time"," and ",[60,69,70],{},"end_time"," parameters.",[15,73,74],{},"Dates can also be specified in three different ways:",[76,77,78,85,98],"ol",{},[79,80,39,81,84],"li",{},[60,82,83],{},"date"," to request departures on a specific date.",[79,86,39,87,90,91,94,95],{},[60,88,89],{},"relative_date"," to automatically select ",[60,92,93],{},"TODAY"," or the next occurrence of the named day, e.g. ",[60,96,97],{},"FRIDAY",[79,99,39,100,103],{},[60,101,102],{},"service_date"," to specify an explicit GTFS service date.",[105,106,107,108,119],"info",{},"\n  ",[15,109,110,111,67,113,115,116,118],{},"Both ",[60,112,83],{},[60,114,89],{}," will correctly translate GTFS calendar.txt\u002Fcalendar_date.txt semantics into normal calendar dates with 24 hour days. That is, the results may include departures from the previous GTFS service date that occur after midnight and\u002For from the early morning of the subsequent GTFS service date. The ",[60,117,102],{}," parameter will restrict the search to only trips and departures for that specific GTFS service date.",[15,120,121],{},"This flexibility is provided because some users need \"wall clock\" times, while other users need results strictly tied to the GTFS service date model.",[105,123,107,124],{},[15,125,126,127,129,130,133,134,137,138,141,142,145],{}," The plain day of week values (e.g. ",[60,128,97],{},") will select the next time that day of the week occurs, inclusive of the current date. ",[60,131,132],{},"NEXT_"," values will select the next time that day of week occurs, not inclusive of the current date. For instance, if the current weekday is Monday, ",[60,135,136],{},"MONDAY"," will return the current date, and ",[60,139,140],{},"NEXT_MONDAY"," will return the next Monday, seven days from now. ",[60,143,144],{},"TUESDAY"," would select the same date in both circumstances, e.g. the day after today.",[33,147,149],{"id":148},"how-are-departure-times-calculated","How are departure times calculated?",[15,151,152,153,156],{},"Transitland calculates ",[41,154,155],{},"scheduled arrivals\u002Fdepartures"," from static GTFS feeds using the following approaches:",[76,158,159,166,169],{},[79,160,161,162,165],{},"The scheduled arrival and\u002For departure times for a given stop, as defined in a static GTFS feed's ",[60,163,164],{},"stop_times.txt"," file.",[79,167,168],{},"If the static GTFS feed does not provide an arrival or departure time for the specified stop, Transitland will interpolate times between \"timepoint\" stops before and after the specified stops.",[79,170,171,172,175,176,179],{},"When available, Transitland will make use of ",[60,173,174],{},"shape_dist_traveled"," values in ",[60,177,178],{},"shapes.txt"," to improve interpolation accuracy.",[15,181,182,183,186,187,190],{},"For operators that also provide GTFS Realtime feeds with ",[60,184,185],{},"TripUpdates",", Transitland also provides ",[41,188,189],{},"real-time arrivals\u002Fdepartures",". Real-time and scheduled values are listed separately in API responses. Note that \"added\" trips will only have real-time values, but not scheduled values.",[105,192,107,193],{},[15,194,195,196,31],{},"See also ",[22,197,199],{"href":198},"\u002Fdocumentation\u002Fconcepts\u002Fsource-feeds#gtfs-realtime-feed-fetching-and-caching","GTFS Realtime feed fetching and caching",[33,201,203],{"id":202},"limitations","Limitations",[205,206,207,217],"ul",{},[79,208,209,210,213,214,216],{},"For operators that provide GTFS Realtime feeds with ",[60,211,212],{},"VehiclePositions"," (but not ",[60,215,185],{},"), Transitland does not use vehicle positions to independently estimate real-time arrivals\u002Fdepartures.",[79,218,219,220,223,224,226],{},"For operators that define route schedules using ",[60,221,222],{},"frequencies.txt"," (a much less popular approach than using ",[60,225,164],{},"), Transitland does not currently calculate stop departure times.",[228,229],"hr",{},[231,232],"openapi-endpoint",{"doc":233,"path":234,":heading-level":235},"rest","\u002Fstops\u002F{stop_key}\u002Fdepartures","3",{"title":237,"searchDepth":238,"depth":238,"links":239},"",2,[240],{"id":12,"depth":238,"text":13,"children":241},[242,244,245,246],{"id":35,"depth":243,"text":36},3,{"id":54,"depth":243,"text":55},{"id":148,"depth":243,"text":149},{"id":202,"depth":243,"text":203},"Get scheduled and real-time departures for a stop with the Transitland v2 REST API, including date and time window parameters and how times are calculated.","md",{"layout":250,"template":251},"documentation","api-reference",true,"\u002Fdocs\u002Frest-api\u002Fdepartures",{"title":5,"description":247},"docs\u002Frest-api\u002Fdepartures","Ap7RuyfxWQ4kp7QMmP6LR-VOWAmCtNAfCaiVfV3sr1c","2026-10-06T21:54:02-07:00",{},{},{},{},1792376828864]