1.Overview
The developer encapsulates the corresponding parameters as required to cancel the room card.The issuance, card reading, and logout interfaces of the proximity card require the user to
download the lock dispenser application to match the interface for card issuance, card reading, logout, etc.This feature requires administrators to turn on issuing print permissions for members in member management.。
2.Request address
3.Request method
4. Parameter specification
Attribute |
Type |
Constraint |
Explanation |
sig |
String |
Required |
Request signature |
issueMac |
String |
Required |
MAC address of the Card issuer, please ignore this parameter when the lock types are QRLOCK and RFLOCK-V9
|
accountSid |
String |
Required |
Developer Account SID, the unique identifier of developer(32 characters of letters and numbers).
|
communityNo |
String |
Required |
Community No. |
serialNum |
String |
Required |
Inductive card serial number, derived from the card reader interface |
creatorAreaCode |
String |
Optional |
Area code in front of the app phone number(对应 creatorMobile,填了creatorMobile则当前Required parameters必填) |
creatorMobile |
String |
Optional |
Mobile number, this mobile number user should be the same as the application user(Either CreatorMobile or CreatoreMail must be filled in. If both are filled in, CreatorMobile will prevail) |
creatorEmail |
String |
Optional |
The mailbox, this mailbox user should be the same as the application user(Either CreatorMobile or CreatoreMail must be filled in. If both are filled in, CreatorMobile will prevail) |
creatorPassword |
String |
Required |
User password encrypted by md5, corresponding to the user in the creator account field |
operateCardType |
String |
Required |
The type of induction card for the operation. Lock types can be viewed in the web end room management of lock cabinets, when the lock type is RFLOCK-V9 pass 2, lock type is QRLOCK pass 3, the remaining lock types are all passed to 4 (the remaining lock types include QRALOCK, QRBLOCK, QRMLOCK, QRNLOCK) |
5.Signature generation rule
accountSid、communityNo、issueMac、serialNum、creatorAreaCode、creatorMobile、creatorPassword、authToken然后使用md5进行Encrypt后获得sig,authToken由Developer资料中Obtain。
When the CreatorAreaCode and CreatorMobile are not empty, the concatenation string is as follows, and then MD5 is used to get the sig:
str="98651082ab89c3f1b50f35caf794179f13168799467C778A6C7D9C45678610000000000bbc69d27003568a7a94626ce4337bc9de687bc93c89b9b59611de521a70ed4"
sig = md5(str) = "c1d425b5d425d0e776cf387c5118b543"
When the creatorAreaCode and creatorMobile are empty, there is no need to concatenate them because they are empty strings. The concatenate strings are as follows, and then MD5 is used to obtain the sig:
str="98651082ab89c3f1b50f35caf794179f13168799467C778A6C7D9C4567bbc69d27003568a7a94626ce4337bc9de687bc93c89b9b59611de521a70ed4"
sig = md5(str) = "6a9c77bc3252025bfc02c67f49b833ad"
6.Request samples
content-type:application/x-www-form-urlencoded
issueMac=7C778A6C7D9C&accountSid=98651082ab89c3f1b50f35caf794179f&communityNo=1316879946&serialNum=4567&creatorAreaCode=86&creatorMobile=10000000000&creatorPassword=49dec5fb8af4eeef7c95e7f5c66c8ae6&operateCardType=4&sig=c1d425b5d425d0e776cf387c5118b543
Successful result:
{ "status": 200, "info": "success" }
Failure reason returning:
{ "status": 6200, "info": "Cancelled card 错误" }
7. SDK