v3 schedules API does not work before 6am

[Eric Hynds]

This is a weird one, but I noticed that the schedules API does not work before 6am. All calls eventually timeout while waiting for a response. I started noticing this on Monday.

Example call: http://api-v3.mbta.com/schedules?api_key=XXXXXX&filter[route]=CR-Worcester

[Developer at MBTA]

Hi Eric,

It looks like the API calls you're making have two additional parameters: "timeout" and "gzip". Is it possible that they're meant as parameters to your HTTP client?

thanks,

developer@mbta

[Eric Hynds]

Thanks, yes those were supposed to be HTTP client options and not query parameters! That should be fixed now.

However, I wasn't able to access the schedule route through Chrome this morning either.

[Developer at MBTA]

Hi Eric,

API V3 is not provided over insecure HTTP, only over HTTPS.

Give https://api-v3.mbta.com/schedules/?filter[route]=CR-Worcester&api_key=XXXXXX a try!

thanks,

developer@mbta

[Eric Hynds]

Well that would certainly explain it. Thanks!

[Eric Hynds]

OK, I think I got to the bottom of it. This may be me misunderstanding how the min_time filter works, but a min_time of 02:00 or 03:00 returns no data for every line.

No data: https://api-v3.mbta.com/schedules/?filter[route]=CR-Worcester&filter[min_time]=3:00
Data: https://api-v3.mbta.com/schedules/?filter[route]=CR-Worcester&filter[min_time]=4:00

[Developer at MBTA]

Hi Eric,

That was a bug in the API: it's since been resolved.

Thanks,

developer@mbta

[Eric Hynds]

Thank you!