Support more robust HTTP API

[Reisen-Wandern-Tauchen]

Hi Reese,

and one more question, that I thought should have it's own place for other to find more easily.

If I wanted to connect with the API, lets say by a PHP script run on the backend of my webserver, what would be the flow through the API calls?
I do understand, that the first call should / needs to be some kind of authentication token. Is this just some kind of username/password handed over in the HTTP header?

I think once I understand how this needs to be done I can most likely work myself through the rest of the API.

May you have some example how to create and hand over that authentication token to openFSD?
Probably, I'm just not smart enough to get the strings together... 🤔🤷‍♂️

Cheers,
Chris

[renorris]

There's no robust API key system in place quite yet. This will come in a future release. Right now the cid and password are sent as URI parameters to /api/v1/login, which returns a token cookie. This is used to make further requests to the API. https://github.com/renorris/openfsd/blob/main/web/README.md.

[Reisen-Wandern-Tauchen]

Ah, I see! Will try and test it somewhere the next 2 weeks or so. I'm still a bit busy at the moment. 😉
Thanks for your quick reply!