a) Web applications:
If you are programming a web application you can authenticate a user and get his/her personal data afterwards by first sending him/her to the authentification page on our site (https://www.44044.com/applications/appLogin/?app_id=123xxx789xxx345xxx20). The user will log in on our site (authentification) and gets redirected to the Callback-URL that you specified in your developer account with the individual app_token for the user attached. You can store the app_token for the user in order to authenticate him/her in the future. The user can disable the app_token by logging out in your application (see call no 8.) or disabling the app_token in my hiogi on the site.
b) Desktop applications:
If you are programming a desktop application and you want to authenticate a user in order to get his personal data, you first need to get an app_token for the user by using the call described below before you can redirect the user to the authentification page already with an app_token attached (http://www.44044.com/applications/appLogin/?app_id=123xxx789xxx345xxx20&app_token= tt3xxxt89xxxt45xxx20). Once the user logged in with his/her username and password on the authentification page the app_token becomes activated and you can pull the personal data for that user. The user can disable the app_token by logging out in your application (see call no 8.) or disabling the app_token in my hiogi on the site.
Note: The app_token will expire after 7 days of user inactivity.
URL: https://api.hiogi.net/1.0/auth/get_app_token.format
Formats: xml, json
Parameters:
-
# app_id | Your application ID
Required | GET
-
# callback | Callback function wrapper for cross domain JSON requests (JSONP)
Optional | GET
Example XML result