User Information API

User Registration

POST https://service.xxx.com/platformapi/chainup/open/user/registration

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

Headers

Name	Type	Description
Content-Type	String	application/json

Name

Type

Description

Content-Type

String

application/json

Request Body

Name	Type	Description
app_id*	String	Merchant unique identifier appKey
time	String
data	String
sign	String

Name

Type

Description

app_id*

String

Merchant unique identifier appKey

time

String

data

String

sign

String


{
    "code": "0",
    "msg": "suc",
    "data": "",
    "sign": ""
}


data:
{
    "uid": 2000000,//user id
    "inviteCode": "AAAAAA"//Current user's invitation code
}

The following are the parameters involved in rsa encryption:

The phone number and email fields are optional, but if you choose to fill in either one of them, you can only provide either the phone number or the email. You cannot fill in both fields simultaneously.

name	type	required	example	Description
mobileNumber	String	NO	09011223	Phone number and email can only be filled in one of them
email	String	NO	xxxxx@.com	Phone number and email can only be filled in one of them
countryCode	String	NO	93	Country dialing code for the phone number
password	String	YES	TtEest19121	Password
invitedCode	String	YES	QSKNOQQQ	Invitation code

name

type

required

example

Description

mobileNumber

String

09011223

Phone number and email can only be filled in one of them

String

xxxxx@.com

Phone number and email can only be filled in one of them

countryCode

String

Country dialing code for the phone number

password

String

YES

TtEest19121

Password

invitedCode

String

YES

QSKNOQQQ

Invitation code

User Registration Information

POST https://service.xxx.com/platformapi/chainup/open/user/reg_info_list

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

Query Parameters

Name	Type	Description
page	String	Page number for pagination, defaults to 1 if not specified
pageSize	String	Number of items per page, defaults to 100 if not specified
regStartTime*	String	Start registration time (13-digit timestamp)

Name

Type

Description

page

String

Page number for pagination, defaults to 1 if not specified

pageSize

String

Number of items per page, defaults to 100 if not specified

regStartTime*

String

Start registration time (13-digit timestamp)

Headers

Name	Type	Description
Content-Type	String	application/json

Name

Type

Description

Content-Type

String

application/json

Request Body

Name	Type	Description
app_id*	String	Merchant unique identifier appKey
time	String
sign	String
data	String

Name

Type

Description

app_id*

String

Merchant unique identifier appKey

time

String

sign

String

data

String

{
  "code": "fugiat in reprehenderit",
  "msg": "sint Excepteur non in",
  "data": "",
  "sign":""
}

data:
{
    "userInfoList": [
      {
        "uid": 23000, // User UID
        "mobileNumber": "9989921", // Mobile number
        "email": "www@.com", // Email
        "inviteCode": "SDONOQWE", // Invitation code
        "pid": "3999009" // Parent UID
      }
    ],
    "count": 62869161.58626932
  }

The following are the parameters involved in rsa encryption:

name	type	required	example	Description
page	String	NO	1	Page number for pagination, defaults to 1 if not specified
pageSize	String	NO	20	Number of items per page, defaults to 100 if not specified
regStartTime	String	YES	1232123421123	Start registration time (13-digit timestamp)

name

type

required

example

Description

page

String

Page number for pagination, defaults to 1 if not specified

pageSize

String

Number of items per page, defaults to 100 if not specified

regStartTime

String

YES

1232123421123

Start registration time (13-digit timestamp)

Invitation Relationship Query - Superior

Return all superior levels found in the current query, up to a maximum of five levels.

POST https://service.xxx.com/platformapi/chainup/open/user/user_superior

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

Headers

Name	Type	Description
Content-Type	String	application/json

Name

Type

Description

Content-Type

String

application/json

Request Body

Name	Type	Description
app_id*	String	Merchant unique identifier appKey
sign	String	Signature
data	String
time	String

Name

Type

Description

app_id*

String

Merchant unique identifier appKey

sign

String

Signature

data

String

time

String

{
  "code": "fugiat",
  "msg": "sed occaecat nisi fugiat",
  "data": "",
  "sign":""
}

data:

{
        "user": {
            "uid": 230001, // User ID
            "inviteCode": "WEQSDA", // Invitation code
            "invitedCode": "OONSIAD", // Invited code
            "invitedUid": 2300002 // Inviter's UID
        },
        "level1": {
            "uid": 230003, // User ID
            "inviteCode": "SDKKCNASD", // Invitation code
            "invitedCode": "SDOMMQWE", // Invited code
            "invitedUid": 2399901 // Inviter's UID
        },
        "level2": {
            "uid": 230003, // User ID
            "inviteCode": "SDKKCNASD", // Invitation code
            "invitedCode": "SDOMMQWE", // Invited code
            "invitedUid": 2399901 // Inviter's UID
        }
    }

The following are the parameters involved in rsa encryption:

name	type	required	Description
openId	String	NO	Choose either openid, emailOrPhone, with uid taking priority
uid	String	NO	user ID
emailOrPhone	String	NO	Mobile phone number

name

type

required

example

Description

openId

String

Choose either openid, emailOrPhone, with uid taking priority

uid

String

user ID

emailOrPhone

String

Mobile phone number

Invitation Relationship Query - Subordinate

POST https://service.xxx.com/platformapi/chainup/open/user/user_invite

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

Headers

Name	Type	Description
Content-Type	String	application/json

Name

Type

Description

Content-Type

String

application/json

Request Body

Name	Type	Description
app_id*	String	Merchant unique identifier appKey
sign	String	Signature
data	String
time	String

Name

Type

Description

app_id*

String

Merchant unique identifier appKey

sign

String

Signature

data

String

time

String

{
  "code": "0",
  "msg": "suc",
  "data": "",
  "sign":""
}

data:
{
    "levelOneCount": 4, // Level 1 count
    "levelTwoCount": 9, // Level 2 count
    "cuerrentUser": {
      "uid": 10002053, // Current user UID
      "nickname": "xuyang", // Current user nickname
      "inviteCode": "EAAAQATW", // Current user invite code
      "invitedUid": -1, // UID of the inviting user, returns -1 if not exist
      "invitedCode": "\"'", // Invited code of the current user, returns an empty string if not exist
      "ctime": "2019-09-02 12:24:36" // Registration time
    },
    "userExtInviteVoList": [ // List of invited users
      {
        "uid": 10002183, // UID
        "nickname": "小明", // Nickname
        "inviteCode": "XXXXXXXX", // Invite code
        "level": 1, // Level 1
        "invitedUid": 10002181, // Inviting user UID
        "invitedNickname": "小花", // Inviting user nickname
        "invitedCode": "XXXXXXXX", // Inviting user invite code
        "phone": "18310479052", // Phone number
        "email": "111@163.com", // Email
        "ctime": "2020-08-22 19:40:18", // Registration time
        "childLevel": [
          {
            "uid": 10002065,
            "nickname": "小明",
            "inviteCode": "XXXXXXXX",
            "level": 2, // Level 2
            "invitedUid": 10002183,
            "invitedNickname": "小花",
            "invitedCode": "XXXXXXXX",
            "phone": "18210479051",
            "email": "111@163.com",
            "ctime": "2020-04-09 20:52:26"
          },
          {
            "uid": 10002065,
            "nickname": "小明",
            "inviteCode": "XXXXXXXX",
            "level": 2,
            "invitedUid": 10002183,
            "invitedNickname": "小花",
            "invitedCode": "XXXXXXXX",
            "phone": "18210479051",
            "email": "111@163.com",
            "ctime": "2020-04-09 20:52:26"
          },
          {
            "uid": 10002065,
            "nickname": "小明",
            "inviteCode": "XXXXXXXX",
            "level": 2,
            "invitedUid": 10002183,
            "invitedNickname": "小花",
            "invitedCode": "XXXXXXXX",
            "phone": "18210479051",
            "email": "111@163.com",
            "ctime": "2020-04-09 20:52:26"
          },
          {
            "uid": 10002065,
            "nickname": "小明",
            "inviteCode": "XXXXXXXX",
            "level": 2,
            "invitedUid": 10002183,
            "invitedNickname": "小花",
            "invitedCode": "XXXXXXXX",
            "phone": "18210479051",
            "email": "111@163.com",
            "ctime": "2020-04-09 20:52
            }]
  ]
}

The following are the parameters involved in rsa encryption:

name	type	required	example	Description
openId	String	NO		Choose either openid, emailOrPhone, with uid taking priority
uid	String	NO		user ID
emailOrPhone	String	NO		Mobile phone number
page	String	YES	1	Page number for pagination, defaults to 1 if not specified
pageSize	String	YES	20	Number of items per page, defaults to 100 if not specified

name

type

required

example

Description

openId

String

Choose either openid, emailOrPhone, with uid taking priority

uid

String

user ID

emailOrPhone

String

Mobile phone number

page

String

YES

Page number for pagination, defaults to 1 if not specified

pageSize

String

YES

Number of items per page, defaults to 100 if not specified

User Identity Verification

POST https://service.xxx.com/platformapi/chainup/open/user/verifyUserIdentity

It is necessary to package the data in the parameter table into JSON strings and use rsa for parameter encryption and signature as data and sign in the body

Headers

Name	Type	Description
Content-Type	String	application/json

Name

Type

Description

Content-Type

String

application/json

Request Body

Name	Type	Description
app_id*	String	Merchant Unique Identifier (appKey)
time	String
sign	String
data	String

Name

Type

Description

app_id*

String

Merchant Unique Identifier (appKey)

time

String

sign

String

data

String


{
    "code": "0",
    "msg": "suc"
}

The following are the parameters involved in rsa encryption:

name	type	required	example	Description
uid	String	YES	230000	User ID
countryCode	String	YES	93	Country code. You need to enter the correct "code", which can be obtained from the left-hand side country code list.
certificateNumber	String	YES	211111111111	ID number
familyName	String	YES	test	Last name
name	String	YES	test	First name
firstPhoto	String	YES		ID photo, only supports online image URLs, maximum of three inputs, separated by commas. Example:"https://oss.com.https://oss.com,https://oss.com"

name

type

required

example

Description

uid

String

YES

230000

User ID

countryCode

String

YES

Country code. You need to enter the correct "code", which can be obtained from the left-hand side country code list.

certificateNumber

String

YES

211111111111

ID number

familyName

String

YES

test

Last name

name

String

YES

test

First name

firstPhoto

String

YES

ID photo, only supports online image URLs, maximum of three inputs, separated by commas. Example:"https://oss.com.https://oss.com,https://oss.com"

POST https://service.xxx.com/platformapi/chainup/open/user/getUserHistoryLogin

Headers

Name	Type	Description
Content-Type	String	application/json

Name

Type

Description

Content-Type

String

application/json

Request Body

Name	Type	Description
appKey*	String	Merchant Unique Identifier (appKey)
sign*	String
uid*	String	User ID
endDate	String	end time 2024-00-00 00:00:00
startDate	String	start time 2024-00-00 00:00:00

Name

Type

Description

appKey*

String

Merchant Unique Identifier (appKey)

sign*

String

uid*

String

User ID

endDate

String

end time 2024-00-00 00:00:00

startDate

String

start time 2024-00-00 00:00:00

{
    "code": "0",
    "msg": "suc",
    "data": {
        "count": 10,
        "HistoryLogin": [
           {
                "id": 2323332,
                "uid": 2324288,//UID
                "lgType": 1,// Login type，1：phone number，2：email，3：WeChat，4：QQ，5：APP QR code 
                "lgPlatform": 3,//Login platform，1：WEB，2：H5，3：APP ,4 : OAUTH
                "lgSystem": "web",//Login system，e.g.‘android’，‘ios
                "lgIp": "111.203.241.52",// Login IP address
                "lgStatus": 1,// Login status，1：success，2：failure
                "lgInTime": 1598352251000//User login time
            },
            {                
                "id": 2323332,
                "uid": 2324288,//UID
                "lgType": 1,// Login type，1：phone number，2：email，3：WeChat，4：QQ，5：APP QR code 
                "lgPlatform": 3,//Login platform，1：WEB，2：H5，3：APP ,4 : OAUTH
                "lgSystem": "web",//Login system，e.g.‘android’，‘ios
                "lgIp": "111.203.241.52",// Login IP address
                "lgStatus": 1,// Login status，1：success，2：failure
                "lgInTime": 1598352251000//User login time
            }
        ]
    }
}

PreviousUser Trade Query NextContract transaction

Last updated 6 months ago

User Registration

Headers

Request Body

User Registration Information

Query Parameters

Headers

Request Body

Invitation Relationship Query - Superior

Return all superior levels found in the current query, up to a maximum of five levels.

Headers

Request Body

Invitation Relationship Query - Subordinate

Headers

Request Body

User Identity Verification

Headers

Request Body

get user history login

Headers

Request Body