This authorization mechanism is different from Oauth API authorization, which is equivalent to obtaining authorization on a webpage. In theory, it can have the ability of a webpage version, but developers need to refer to the HTTP requests on the webpage themselves!

step 1:

First Step

Go to client page: https://www.febbox.com/open/client
Create a client and obtain the client ID
redirect URIs :
After allowing login, the webpage will redirect to this URL and the login credentials will be passed through GET method

Second Step

Create login link
https://www.febbox.com/login/google?client_id=[client_id]&jump=[redirect_uri]

After the user successfully logs into Febbox through Google authentication, the system will redirect to the pre-set URL and pass the auth_token parameter，
Exp:https://www.domain.com/febbox?auto_token=xxxxxxxxxxx

Third Step

Put the obtained auth_token into the cookie, with the key being UI, and you can use some APIs on the webpage

Exp:
curl 'https://www.febbox.com/xxxxx' -H 'cookie: ui=[auth_token]'

web api authorize document

step 1:#

step 1: