Skip to content
This repository has been archived by the owner on Dec 6, 2022. It is now read-only.

OpenAPI 3.1 specification for the Metro Transit NexTrip API 🚍

Notifications You must be signed in to change notification settings

kanadgupta/metrotransit-nextrip-oas

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 

History

29 Commits
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Metro Transit NexTrip API Definition 🚍

This provides an OpenAPI definition for the Metro Transit NexTrip API.

ReadMe Documentation πŸ¦‰

The OpenAPI file in this repository backfills the server object so the API can be used in these unofficial docs, hosted on ReadMe. The file is syncing to ReadMe via a GitHub Action.

Update (December 2022)

Metro Transit released version 21 of the NexTrip API, along with an entire OpenAPI definition to boot! See a screenshot of the deprecation notice below (grabbed from here):

A screenshot of a deprecation notice that reads: 'NOTICE: NexTrip version 1 (https://svc.metrotransit.org/nextrip/) is deprecated and will be removed at the end of June '22.
Version 2 documentation can be found at https://svc.metrotransit.org/swagger.'

This repository was created a few years ago to document version 1 of the API, back when it was primarily returning XML responses and the only official documentation was a static, non-interactive page with a list of endpoints. How far we've come πŸ₯Ή

While this is all very exciting news, this repository is no longer a good source-of-truth for the NexTrip API and you should refer to the official docs instead.

If you're looking for an official demo of the rdme GitHub Action, please check out this repository.

Footnotes

  1. As of this writing (12/6/2022), the docs say that the API is still in beta and is subject to change. ↩

Releases

No releases published

Packages

No packages published