Anonymous Login
POST/auth/v1/signin/anonymously
For the same device ID, at most one anonymous user can be registered, and an access_token for that anonymous user is generated.
Request
Query Parameters
The client ID corresponding to the application, which can be obtained from Cloud Development Platform --> Authentication --> Development Settings. Defaults to the environment ID and can be omitted.
Header Parameters
Required for anonymous login. The device ID of the currently logged-in device. The client should randomly generate and cache this value. This parameter is used to calculate the user ID during anonymous login. If not cached, the anonymous user will log in again and the user ID will change.
- application/json
Body
Responses
- 200
- 400
- 403
- 500
A successful response.
Response Headers
- application/json
- Schema
- Example (from schema)
- Example
Schema
Always returns Bearer
Token used to access the Cloud Development HTTP API, with a maximum length of 4096 characters
When the access_token expires, it can be refreshed using the refresh_token to obtain a new access_token. The default expiration time is 31 days. Maximum length is 128 characters
Expiration time of the access_token in seconds
{
"token_type": "string",
"access_token": "string",
"refresh_token": "string",
"expires_in": 0,
"scope": "string",
"sub": "string",
"groups": [
"string"
]
}
{
"token_type": "Bearer",
"access_token": "eyJhbGciOiJSUzI1NiIsImtpZCI6IjlkMWRjMzFlLWI0ZDAtNDQ4Yi1hNzZmLWIwY2M2M2Q4MTQ5OCJ9.eyJpc3MiOiJodHRwOi8vbG93Y29kZS01ZzlhYzIwdTJhMjdkYTQ2LmFwLXNoYW5naGFpLnRjYi1hcGkudGVuY2VudGNsb3VkYXBpLmNvbSIsInN1YiI6IjdmdDlXUnJlbVhyei1UZmdvQVI5VXciLCJhdWQiOiJBT0o4eUFBQnpOc01YZjBJY0tjIiwiZXhwIjoxNzM0Njg5NTU3LCJpYXQiOjE3MzQ2ODIzNTcsIm5vbmNlIjoiNmE4ZmNmM2YtY2NkOC00NjJhLTgwNmEtZGE0ZWFlYzc5YjUyIiwiYXRfaGFzaCI6Ii1sd2RDaVhqUXRLY1FPZkM4Y1VYYXciLCJuYW1lIjoiQW5vbnltb3VzIiwic2NvcGUiOiJhbm9ueW1vdXMiLCJwcm9qZWN0X2lkIjoibG93Y29kZS01ZzlhYzIwdTJhMjdkYTQ2IiwibWV0YSI6eyJ3eE9wZW5JZCI6IiIsInd4VW5pb25JZCI6IiJ9LCJ1c2VyX2lkIjoiN2Z0OVdScmVtWHJ6LVRmZ29BUjlVdyIsInVzZXJfdHlwZSI6IiJ9.m0BgSPuw3rs-mU-SfdYz85LmmWnZIOmlanRsMx0U8IrkZTAptRvaNYBxyoRGuKB2DlsF8MsAG7DNSqNpK2fasHGT1mP3l3YKXwoApRuo_JtTuMSE95guRoiXuu60fJIBs_5lRHv6vXgtQ3p9t9erbtcePXbm1Ux7BtGD71yN7gwaJXmGA73Ck7ZI-0tpyV93gUJGKhO3T7kHNbEOyX_1jJ74W5cH_zK5AVAXi6NhCrtT46MiANdWUDORNBbjFcVYjWZggTB9EWU6nnj_YWQO9IiDJuKWBWsJcMakcxMs2Vf0r8N78QR0w1edhgoX3QqcKSfkGmrQZE9Ln6iga4D6wA",
"expires_in": 7200,
"scope": "anonymous",
"sub": "7ft9WRremXrz-TfgoAR9Uw"
}
- invalid_argument Please add the device id (x-device-id) in the request Header, as it is not provided.
- unimplemented Please contact the administrator to enable Anonymous Login. Anonymous Login is not enabled. Go to the Cloud Development Platform to enable it.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{}
Response Headers
- application/json
- Schema
- Example (from schema)
- Example
Schema
{}
{
"error": "permission_denied",
"error_code": 7,
"error_description": "cors permission denied, please check if lowcode-5g9ac20u2a27da47-1307578329.tcloudbaseapp.com in your client AOJ8yAABzNsMXf0IcKc domains"
}
An unexpected error response.
Response Headers
- application/json
- Schema
- Example (from schema)
Schema
{
"error": "string",
"error_code": 0,
"error_description": "string"
}