Difference between revisions of "LoginApplicationToken"
Jump to navigation
Jump to search
| (4 intermediate revisions by one other user not shown) | |||
| Line 30: | Line 30: | ||
|Returns= | |Returns= | ||
| + | Returns a JSON containing the Login object. | ||
| + | Example: | ||
| + | |||
| + | { | ||
| + | : [[Login]] Object | ||
| + | } | ||
| + | |||
|Exceptions= | |Exceptions= | ||
| − | + | <span style="color: #a11;">TO BE COMPLETED</span> | |
|Cache= | |Cache= | ||
| Line 41: | Line 48: | ||
|VersionHistory= | |VersionHistory= | ||
| − | + | <span style="color: #a11;">TO BE COMPLETED</span> | |
|SeeAlso= | |SeeAlso= | ||
}} | }} | ||
Latest revision as of 13:30, 23 February 2016
Description
Login Application Token do the login in the application using a previous token generated by the method GetApplicationToken in the RegistrationService.
Parameters
- deviceType (int, required)
- The device type code (see #DeviceTypeCodes enumeration to know the list of device types allowed)
- instanceId (int, required)
- The id of the instance (OB) for the current environment. This ID might vary depending on the environment.
- deviceId (string, required)
- Device ID that uniquely identifies the device. This is usually a device factory identifier. In order to login with a device as TrustedDevice, the user needs to previously register the device as trusted device (using Registration Service methods).
- applicationtoken (string, required)
- A valid token for identifying the API session context and logged user.
Returns
Returns a JSON containing the Login object. Example:
{
- Login Object
}
Exceptions
TO BE COMPLETED
Caching
This method is not cached.
Known issues
None
Version history
TO BE COMPLETED
