-
Notifications
You must be signed in to change notification settings - Fork 7
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
Tussam API has changed #37
Comments
Hi @alesanmed! Thanks for the heads up :) Turns out the API is wrapped in a middleware server, so it can be fixed without updating the app. I know about the new JSON API, but didn't find time to migrate it. I might try to do it during the weekend, but if you have knowledge about Java and Spring feel free to open a PR ;) |
I'm also facing this problem with the Alexa skill (https://www.amazon.es/Antonio-G%C3%A1mez-Autobuses-de-Sevilla/dp/B07G19L52X). Currently I'm modeling the new Tussam REST API using OpenAPI, so that it is easier to automatically consume the API. As soon as I finish, I'll share it with you guys. |
Here you have an initial draft of the API docs: https://app.swaggerhub.com/apis/antgamdia/tussam-rest/1.0 :) |
Hello @antgamdia, I'm trying to consume the REST API but I need to authenticate myself and I'm not able to find where to obtain some credentials, would you help me? |
Hello all. Greeting. |
AFAIK, the API still works as in the documentation I posted some time ago. To authenticate, due to recent changes in the authentication system, you need to: either create an account in Tussam (via the phone app, for example) and use these credentials or reach out to |
Thank you, antgamdia. I tried with app credentials but I didn't get, so I have written them, I am waiting a response. Greetings. |
It seems like tussam people have just released a brand new REST API, making this app and others using the old API stop working. Me and a friend already have already done some research about the new API and how it works. If you want further info or need some help for making the required changes in the APP in order to make it work again, just ask for it.
The text was updated successfully, but these errors were encountered: