-
Notifications
You must be signed in to change notification settings - Fork 4
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
API Key provided is not valid #1
Comments
Metlink has this strange setup where in addition to signing up for a developer key, you need to subscribe to the API you want (strange, since they only offer one API). If you go to https://opendata.metlink.org.nz/apis do you have the option to "Subscribe" there? |
Hey there,
I have logged and there are no API's published and no option to subscribe.
However, I do have the option to "Get" various gtfs datasets.. Are there
particular datasets that I should choose to get?
Thanks,
…On Sat, 19 Jun 2021 at 12:30, Jason Rumney ***@***.***> wrote:
Metlink has this strange setup where in addition to signing up for a
developer key, you need to subscribe to the API you want (strange, since
they only offer one API).
If you go to https://opendata.metlink.org.nz/apis do you have the option
to "Subscribe" there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJITBOJCYXJKCTRJLCKM263TTPQLLANCNFSM466ONU6A>
.
|
Hi again,
I browsed the site again, following the links on the site rather than the
direct URL; doing it this way gave me the option to subscribe.
Everything is working now. Thanks!
…On Sat, 19 Jun 2021 at 12:30, Jason Rumney ***@***.***> wrote:
Metlink has this strange setup where in addition to signing up for a
developer key, you need to subscribe to the API you want (strange, since
they only offer one API).
If you go to https://opendata.metlink.org.nz/apis do you have the option
to "Subscribe" there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJITBOJCYXJKCTRJLCKM263TTPQLLANCNFSM466ONU6A>
.
|
Thanks. I've added a hint to that error message, as I think a lot of people will miss this. |
make-all
added a commit
that referenced
this issue
Apr 8, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
Thank you for writing this integration. I have the below issue after pasting in my valid API key using the UI integration.
Error: "The api key provided is not valid."
When I configure the integration in my sensor.yaml; results are unavailable (I configure my sensors in a sperate file).
Sensor.yaml
api_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
stops:
route: CP
destination: 3244
num_departures: 3
The text was updated successfully, but these errors were encountered: