inconsistent use of http and https

[RavinMaddHatter]

the folowing endpoints are not accesible via https:// api target

/servers
/server/:id/users
/server/:id/database
/server/:id/players

I am not a fan of sending the api key over http, these targets should be targetable via https

[subtato]

Hey there! 👋

Thanks for the report! Apologies for the delay in response; it's not often we see reports here on GitHub, haha.

I'm not seeing anywhere stating that the API key should be sent over plain HTTP; all of our documentation appears to show HTTPS. Where are you seeing otherwise? If you're encountering an SSL certificate error, you'll need to ensure that your computer or server's time is set correctly, followed by potentially using alternative DNS servers (we'd recommend 1.1.1.1).

Regarding the API calls not being accessible: can you provide what error message(s) you're seeing? All of the paths you've mentioned are working on my end.
We use these endpoints in our production control panel within the user's browser, so you should be able to access them outright via your flavor of web browser(s) to see the response of these API calls after logging into Prisma.
As an example -

The only outlier here is that the /server/:id/players route may be defunct due to functionality being changed over time and it not being actively used within the control panel. We'll be fixing this in a future update, as well as some potential additional informational pages.

[RavinMaddHatter]

I submitted a pull request for a python api that works, you can look at the way I was executing the posts. Some of them. Seem to be unhappy when I use https. It has been a while.

…

On Tue, Apr 27, 2021, 3:49 PM Bill Ewing ***@***.***> wrote: Hey there! 👋 Thanks for the report! Apologies for the delay in response; it's not often we see reports here on GitHub, haha. I'm not seeing anywhere stating that the API key should be sent over plain HTTP; all of our documentation appears to show HTTPS. Where are you seeing otherwise? If you're encountering an SSL certificate error, you'll need to ensure that your computer or server's time is set correctly, followed by potentially using alternative DNS servers (we'd recommend 1.1.1.1). Regarding the API calls not being accessible: can you provide what error message(s) you're seeing? All of the paths you've mentioned are working on my end. We use these endpoints in our production control panel within the user's browser, so you should be able to access them outright via your flavor of web browser(s) to see the response of these API calls after logging into Prisma. As an example - [image: image] <https://user-images.githubusercontent.com/1311708/116321378-8a6cbf80-a77f-11eb-8466-d5da1b39777d.png> The only outlier here is that the /server/:id/players route *may* be defunct due to functionality being changed over time and it not being actively used within the control panel. We'll be fixing this in a future update, as well as some potential additional informational pages. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBUC5AEZ5KQWXYE2XUYZKDTK45PLANCNFSM4XTUP4CQ> .

[subtato]

Gotcha! Honestly, I had assumed it was a dependabot alert... just a side effect of limited use of pull requests in private repos 😂

I'll see what I can test here in the next few days, but I'd anticipate additional details/responses in that regard sometime next week. An upcoming Prisma update is keeping us busy, putting it lightly anyways, haha!

[RavinMaddHatter]

No problem. It has been a while since I submitted so details are fuzzy.

…

On Tue, Apr 27, 2021, 4:04 PM Bill Ewing ***@***.***> wrote: Gotcha! Honestly, I had assumed it was a dependabot alert... just a side effect of limited use of pull requests in private repos 😂 I'll see what I can test here in the next few days, but I'd anticipate additional details/responses in that regard sometime next week. An upcoming Prisma update is keeping us busy, putting it lightly anyways, haha! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBUC5BJEBNV3VSAM6UNJ2DTK47JNANCNFSM4XTUP4CQ> .