Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Last revision Both sides next revision | ||
|
en:biostar_2_api_quickstart_guide [2018/02/27 08:30] jypark [Features] |
en:biostar_2_api_quickstart_guide [2018/02/27 09:05] jypark [Analysis of the source code] |
||
|---|---|---|---|
| Line 46: | Line 46: | ||
| The most important part in this sample application is log-in. Let’s take a look at the function below: | The most important part in this sample application is log-in. Let’s take a look at the function below: | ||
| - | {{:en:web_api_quick_start_-_006.png?nolink&800|}} | + | {{:en:web_api_quick_start_-_006_new.png?nolink&800|}} |
| - | * Line 26: This is the URL that we are using to log in to your local BioStar server. We only allow HTTPS protocol and “api.biostar2.com/v1/” is prefix. “login” after the prefix indicates a behavior or action we want to take. | + | * Line 26: This is the URL that we are using to log in to your local BioStar server. In case of Local API, “http://127.0.0.1:8795/v2/” is prefix. “login” after the prefix indicates a behavior or action we want to take. |
| * Line 27: In this sample code, we use class HttpClient to send a request and receive a response from the BioStar Cloud. | * Line 27: In this sample code, we use class HttpClient to send a request and receive a response from the BioStar Cloud. | ||
| * Line 30: Class JavaScriptSerializer is needed to convert the data into JSON formatted data or parse the JSON formatted data into any format you want. | * Line 30: Class JavaScriptSerializer is needed to convert the data into JSON formatted data or parse the JSON formatted data into any format you want. | ||
| Line 61: | Line 61: | ||
| 2. Retrieving access groups | 2. Retrieving access groups | ||
| - | {{:en:web_api_quick_start_-_007.png?nolink&800|}} | + | {{:en:web_api_quick_start_-_007_new.png?nolink&800|}} |
| * Line 205-209: We first need to check if the login was successfully made and the session ID was stored. | * Line 205-209: We first need to check if the login was successfully made and the session ID was stored. | ||
| Line 71: | Line 71: | ||
| 3. Retrieving events | 3. Retrieving events | ||
| - | {{:en:web_api_quick_start_-_008.png?nolink&800|}} \\ | + | {{:en:web_api_quick_start_-_008_new.png?nolink&800|}} \\ |
| {{:en:web_api_quick_start_-_009.png?nolink&800|}} | {{:en:web_api_quick_start_-_009.png?nolink&800|}} | ||
| Line 81: | Line 81: | ||
| 4. Creating a user | 4. Creating a user | ||
| - | {{:en:web_api_quick_start_-_010.png?nolink&800|}} \\ | + | {{:en:web_api_quick_start_-_010_new.png?nolink&800|}} \\ |
| * Line 99-100: We receive a user input for the ID of a new user. | * Line 99-100: We receive a user input for the ID of a new user. | ||