V8.0 With the API

[Siege]

After 8.0 I think we need a Tutorial on how to get our API working again since now it is another configuration and at least I don't know how to put it right, I would greatly appreciate it.

[XFallSeane]

I highly recommend with each new major update to things you use to look at the new files created at the base of your folders.

 

The server folder has 4 new files at its base, appsetting.json, appsettings.Production.json, self-signed.crt abd self-signed.key.

 

To activate the API you need to activate it by default in appsettings.Production.json, then you will need to run the server in HTTPS which should be functional thanks to the certificates and the key (for your local computer only those there).

 

Then, you just need to put your new url where you use your server: https://localhost:5443 for local servers and on remote servers: https:IpOrDomain:5443

Remember, you need an SSL certificate on your live server for api work.

 

On your internet browser, type the URL that suits you + /api/v1/users (https://localhost:5443/api/v1/users)  if you come across a 404 error everything is good, if you come across an ssl or empty response error there are a few things that are wrong.

[Siege]

Then you just need to put your new URL where you use your server [where are you referring to here? ]

 

To enable the API you need to enable it by default in appsettings.Production.json, then you will need to run the server on HTTPS [in appsettings.Production.json Where specifically should that be changed? ]

 

Port 5443 is a different one, right? It is not the one we use for the server port I imagine.

 

As for the SSL certificate, should it work now? or you have to pay for that service.

 

Then in the Tools API you are supposed to reinstall again to re-enter the installation data to put the https format this time and not the http, right?

 

 

[Siege]

12 hours ago, XFallSeane said:

I highly recommend with each new major update to things you use to look at the new files created at the base of your folders.

 

The server folder has 4 new files at its base, appsetting.json, appsettings.Production.json, self-signed.crt abd self-signed.key.

 

To activate the API you need to activate it by default in appsettings.Production.json, then you will need to run the server in HTTPS which should be functional thanks to the certificates and the key (for your local computer only those there).

 

Then, you just need to put your new url where you use your server: https://localhost:5443 for local servers and on remote servers: https:IpOrDomain:5443

Remember, you need an SSL certificate on your live server for api work.

 

On your internet browser, type the URL that suits you + /api/v1/users (https://localhost:5443/api/v1/users)  if you come across a 404 error everything is good, if you come across an ssl or empty response error there are a few things that are wrong.

 

ERR_SSL_VERSION_OR_CIPHER_MISMATCH  

 

That's what I get in the browser, but it's supposed to already be recognizing it, right? There's just something missing that's not right, right?

[Alphaonic]

You can get the new API working again by starting with a clean config, grabbing the fresh key from the server dashboard, and making sure the port matches what you set in the server’s JSON. I had fewer connection hiccups once I mirrored that setup with a tool I use for messaging projects, whatsapp business api, since it reminded me to double‑check webhook URLs and auth steps the same way.