Skip to Content

Changes for page HTTPS API

Last modified by Devin Chen on 2026/05/12 11:15
From version 9.1
edited by Devin Chen
on 2026/03/19 09:44
Change comment: There is no comment for this version
To version 2.2
edited by Devin Chen
on 2025/09/24 10:06
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -V-Net 2\.0.WebHome
1 +V-Net 2\.0.Operation Manual.WebHome
Content
... ... @@ -3,7 +3,7 @@
3 3  
4 4  
5 5  This standard defines Wecon's proprietary access protocol. Third-party API integration requires explicit authorization through our V-net V2.0 platform, with all API access strictly monitored and regulated. Wecon reserves all rights to interpret and modify these specifications without prior notice.
6 -\\To prevent API abuse,this feature will not be enabled by default for all users. **Access requires submitting an application**, with a monthly free quota of 10,000 times.The free quota will be restored on the 1st of the following month.**(This limitation is only for Wecon API motioned by in this manual)**
6 +\\To prevent API abuse,this feature will not be enabled by default for all users. Access requires submitting an application, with a monthly free quota of 10,000 times.
7 7  {{/warning}}
8 8  
9 9  = 1.Third-party account =
... ... @@ -12,10 +12,20 @@
12 12  
13 13  == 1.1 Create a third-party account ==
14 14  
15 -Please refer to the link below to create a third-party account
15 +(% style="text-align:center" %)
16 +[[image:hj18xtdG0np.png||height="498" width="1200"]]
16 16  
17 -[[How to create a third-party account for V-net API>>doc:V-BOX.FAQ.How to create a third-party account for V-net API]]
18 +(% style="text-align:center" %)
19 +[[image:PixPin_2025-07-09_11-27-51.png]]
18 18  
21 +{{info}}
22 +Noted:
23 +
24 +~1. After clicking "OK", the third-party account password will no longer be visible. Please back it up promptly.
25 +
26 +2.** An admin account only allows to create one third-party account.**
27 +{{/info}}
28 +
19 19  == 1.2 Assign device to third-party account ==
20 20  
21 21  1.choose the third-party account
... ... @@ -38,10 +38,7 @@
38 38  == 2.1 Basic information ==
39 39  
40 40  * (((
41 -**Request url**:
42 -Asean: https:~/~/api.asean.v-iec.com/m16/{acturl}
43 -
44 -EU: https:~/~/api.eu.v-box.net/m16/{acturl}
51 +**Request url**: https:~/~/api.asean.v-iec.com/m16/{acturl}
45 45  )))
46 46  * (((
47 47  **Protocol: **https
... ... @@ -328,15 +328,15 @@
328 328  
329 329  **Step2:**  Get sign (Using the sid obtained from calling the login API;demonstrated here as "e95ae840f7f147718d2b7650abe6c05f")
330 330  
331 -cuid=123456789&lan=zh&mt=255&pid=1&sid=e95ae840f7f147718d2b7650abe6c05f&sv=1.0&ts=1750818494344&key=5cee621329f24e5cbdc43daa959ce9a1
338 +cuid=123456789&lan=zh&machineCode=V1400023040700790f5e19a1b55&mt=255&pid=1&sid=e95ae840f7f147718d2b7650abe6c05f&sv=1.0&ts=1750818494344&key=5cee621329f24e5cbdc43daa959ce9a1
332 332  
333 333  Put the whole string above encrypted by MD5, so will get the value of "sign" 
334 334  
335 -"sign":"2be680121333bf3dc479958efae791e2"
342 +"sign":"f0889257ce45e561959928ba5475fbf1"
336 336  
337 337  **Step4: ** Set wcommon of header
338 338  
339 -{"dap":"","cuid":"123456789","sv":"1.0","mt":"255","lan":"zh","sign":"2be680121333bf3dc479958efae791e2","pid":"1","ts":1750818494344,"sid":"e95ae840f7f147718d2b7650abe6c05f"}
346 +{"dap":"","cuid":"123456789","sv":"1.0","mt":"255","lan":"zh","sign":"f0889257ce45e561959928ba5475fbf1","pid":"1","ts":1750818494344,"sid":"e95ae840f7f147718d2b7650abe6c05f"}
340 340  
341 341  [[image:1750906712204-462.png]]
342 342  
XWiki.XWikiRights[1]
Allow/Deny
... ... @@ -1,0 +1,1 @@
1 +Allow
Groups
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiAgentGroup
Levels
... ... @@ -1,0 +1,1 @@
1 +view