Help Center/ Meeting/ Server API Reference/ Hard Terminal Management/ Managing Activation Codes/ Resetting an Activation Code Using the SN as an Enterprise Administrator
Updated on 2023-12-22 GMT+08:00
Online Debugging
CLI Examples
View PDF
Share

Resetting an Activation Code Using the SN as an Enterprise Administrator

Description

This API is used by an enterprise administrator to reset a hard terminal activation code. The new activation code can be used to activate the hard terminal. This API can be called five times for each hard terminal every 24 hours.

Debugging

You can debug this API in API Explorer.

Prototype

Table 1 Prototype

Request Method

POST

Request Address

/v1/usg/dcs/corp/device/{sn}/activecode

Transport Protocol

HTTPS

Request Parameters

Table 2 Parameters

Parameter

Mandatory

Type

Location

Description

sn

Yes

String

Path

Terminal SN. The value can contain only numbers, letters, and underscores (_).

X-Access-Token

Yes

String

Header

Authorization token. Use the value of accessToken in the response to the request for Authenticating an App ID.

X-Request-Id

No

String

Header

Request ID, which is used for fault tracing and locating. You are advised to use a UUID. If this parameter is not carried, a request ID is automatically generated.

Accept-Language

No

String

Header

Language. Values: zh-CN for Chinese (default) and en-US for English.

country

No

String

Body

Country or region that the mobile number belongs to.

Default value: chinaPR.

emailAddr

No

String

Body

Email address.

NOTE:

The mobile number or email address must be specified. If the enterprise does not enable SMS messages, the email address is mandatory.

smsNumber

No

String

Body

Mobile number. For example, a mobile number in Chinese mainland is +86xxxxxxxxxxx. This parameter is combined with the country parameter.

NOTE:

The mobile number or email address must be specified. If the enterprise does not enable SMS messages, the email address is mandatory.

Status Codes

Table 3 Status codes

HTTP Status Code

Description

200

Operation successful.

400

Invalid parameters.

401

Authentication is not performed or fails.

403

Insufficient permissions.

500

Server exception.

Response Parameters

None

Example Request

POST /v1/usg/dcs/corp/device/asdasfscasd/activecode
Connection: keep-alive
X-Access-Token: stbVbWSIgzfOQ8JnbmPIoBIR3ig8xnVScQOF
Content-Type: application/json
Content-Length: 94
Host: api.meeting.huaweicloud.com 
User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_191)

{
    "smsNumber": "+86***********",
    "country": "chinaPR",
    "emailAddr": "test8@huawei.com"
}

Example Response

HTTP/1.1 200 
Date: Wed, 18 Dec 2019 06:20:40 GMT
Content-Type: application/json;charset=UTF-8
Content-Length: 143
Connection: keep-alive
Pragma: No-cache
Cache-Control: no-cache
Server: api-gateway
X-Request-Id: fbbc91569f0efed914e0427fc2a9c4ac

Error Codes

If an error code starting with MMC or USG is returned when you use this API, rectify the fault by following the instructions provided in Huawei Cloud API Error Center.

Example cURL Command

curl -k -i -H 'content-type: application/json' -X POST -H 'X-Access-Token: stbVbWSIgzfOQ8JnbmPIoBIR3ig8xnVScQOF' -d '{"smsNumber": "+86***********","country": "chinaPR","emailAddr": "test8@huawei.com"}' https://api.meeting.huaweicloud.com/v1/usg/dcs/corp/device/asdasfscasd/activecode