Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Developer Migration from NextBus to Swiftly #73

Open
albertkun opened this issue Dec 14, 2021 · 2 comments
Open

Developer Migration from NextBus to Swiftly #73

albertkun opened this issue Dec 14, 2021 · 2 comments

Comments

@albertkun
Copy link
Collaborator

AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH

@matikin9
Copy link
Collaborator

matikin9 commented Dec 15, 2021

This page needs to be updated: https://developer.metro.net/api/

Sample language/descriptions we can use: https://www.mta.maryland.gov/developer-resources

Use this link for developers to request an API Key from Swiftly: https://forms.gle/hXGY6kRGAChDqWwz5

Thsi is Swiftly's API Docs: https://realtime-docs.goswift.ly/

We can mention that api.metro.net will still exist, but it will continue to pull from the old NextBus feed until we rollout the update that switches over to the Swiftly feed.

Genna can put us in touch with folks at SEPTA, Honolulu, MBTA, to talk about setting up an API pass-through structure and getting all our other systems using api.metro.net.

@albertkun
Copy link
Collaborator Author

albertkun commented Dec 15, 2021

See follow-up issue here: LACMTA/developer-metro-net#2

@matikin9 matikin9 moved this from Todo to Done in Digital Services Tasks Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

No branches or pull requests

2 participants