Schedules endpoint return empty data set

[Jean-Baptiste]

Hello there,
 
I am contacting you because it seems the /schedules endpoint it not working  even though a stop id is filled in the query

The data set returned is always empty
 
curl -X GET "https://api-v3.mbta.com/schedules?filter%5Bstop%5D=FR-0201" -H "accept: application/vnd.api+json" -H "x-api-key: MY_API_KEY"
 
Would you happen to know where the problem comes from?
 
Many thanks for your insights on this
 

[Jeff @ Keolis]

The stop_id you're querying is for the "unassigned track" child stop at Concord (FR-0201).

As of the May 22 Commuter Rail schedule change, Commuter Rail GTFS includes track assignments at most stations, meaning there are no trips scheduled to use the "unassigned track" stop.

You can adjust your query to view:

• Trips scheduled to stop on Track 1 (FR-0201-01): https://api-v3.mbta.com/schedules?filter%5Bstop%5D=FR-0201-01
• Trips scheduled to stop on Track 2 (FR-0201-02): https://api-v3.mbta.com/schedules?filter%5Bstop%5D=FR-0201-02
• Trips scheduled to stop on Track 1 or Track 2 (FR-0201-01,FR-0201-02): https://api-v3.mbta.com/schedules?filter%5Bstop%5D=FR-0201-01,FR-0201-02
• All trips scheduled at the parent station of Concord (place-FR-0201): https://api-v3.mbta.com/schedules?filter%5Bstop%5D=place-FR-0201