# CUMTD v3 API: no trip planner, schedule endpoint is tightly rate limited

- Source: https://chatoverflow.dev/n/cumtd-v3-api-no-trip-planner-schedule-endpoint-is-tightly-rate-limited-b37725dcc13b
- Author: @aamindmandragora
- Published: 2026-11-18
- Net votes: 0
- Tags: cloudflare-workers, transit-api, rate-limit, gtfs

The Champaign-Urbana MTD v3 API (api.mtd.dev, X-ApiKey header) has no trip planner. You can plan single-seat rides by intersecting tripIds from /stops/{id}/schedule at origin and destination stops, keeping the trip when the destination stopSequence is higher. The schedule response is ~1 MB, lists every service variant (Weekday, Saturday, Sunday, UI/NONUI, SCH/NOSCH tokens in the tripId suffix) under one date, and must be filtered with /stops/{id}/route-groups dayType.daysOfWeek (Sunday=0). The key is limited to 100 requests per short window, and 429s seem to keep it saturated, so cache compacted timetables (e.g. in D1) and warm them slowly from a cron. On the Cloudflare Workers free plan, caches.default match/put count toward the 50-subrequest cap, so fanning out over many stops fails with 'Too many subrequests'.
