Skip to main content
POST
/
merchant
/
member
/
delete_totp_device
Admin Owner Or Admin Delete Own's' 2FA Device
curl --request POST \
  --url https://api.unibee.dev/merchant/member/delete_totp_device \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "deviceIdentity": "<string>",
  "memberId": 123
}
'
{
  "code": 123,
  "data": {
    "deviceList": [
      {
        "currentDevice": true,
        "identity": "<string>",
        "ipAddress": "<string>",
        "lastActiveTime": 123,
        "lastLoginTime": 123,
        "lastTotpVerificationTime": 123,
        "name": "<string>",
        "status": true
      }
    ]
  },
  "merchantId": 123,
  "message": "<string>",
  "redirect": "<string>",
  "requestId": "<string>"
}

Endpoint Overview

POST https://api.unibee.dev/merchant/member/delete_totp_device Admin Owner Or Admin Delete Own’s’ 2FA Device

Authorization

All UniBee Merchant API requests require authentication via API key.
HeaderRequiredDescription
AuthorizationYesBearer <your_api_key>
Content-TypeYesapplication/json (for request body)

Parameters

Parameters for this endpoint are listed below. The schema is also shown in the Try it panel.

Request body

NameTypeRequiredDescription
deviceIdentitystringNoDevice Identity
memberIdintegerNoThe unique id of member

Request examples

cURL

curl -X POST "https://api.unibee.dev/merchant/member/delete_totp_device" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "deviceIdentity": "id_example",
  "memberId": 0
}'

Sandbox

curl -X POST "https://api-sandbox.unibee.top/merchant/member/delete_totp_device" \
  -H "Authorization: Bearer YOUR_SANDBOX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "deviceIdentity": "id_example",
  "memberId": 0
}'

Response

Success responses return a JSON envelope with code, data, message, redirect, and requestId. code 0 indicates success.
FieldTypeDescription
codeintegerResponse code. 0 = success
dataobjectResponse payload
data.deviceListarrayThe devices list’
messagestringHuman-readable message
requestIdstringRequest ID for support

Error handling

HTTP statusMeaning
400Bad request — invalid or missing parameters. Check message in the body.
401Unauthorized — missing or invalid API key.
404Not found — invalid path or resource.
500Server error — retry with backoff.
When code in the response body is non-zero, check message for details. Use requestId when contacting support.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
deviceIdentity
string<string>

Device Identity

memberId
integer<int64>

The unique id of member

Response

200 - application/json
code
integer<int>
data
object
merchantId
integer<int64>
message
string<string>
redirect
string<string>
requestId
string<string>