Help Center> Meeting> Server API Reference> Hard Terminal Management> Modifying the Terminal Status in Batches
Updated on 2023-12-22 GMT+08:00
Online Debugging
CLI Examples
View PDF

Modifying the Terminal Status in Batches

Description

This API is used by an enterprise administrator to modify the professional meeting terminal status in batches. If professional meeting terminal resources expire and the number of these terminals in the enterprise exceeds the upper limit, the system disables some terminals at random. In this case, the enterprise administrator can use this API to modify the status of professional meeting terminals.

Debugging

You can debug this API in API Explorer.

Prototype

Table 1 Prototype

Request Method

PUT

Request Address

/v1/usg/dcs/corp/device/status/{value}

Transport Protocol

HTTPS

Request Parameters

Table 2 Parameters

Parameter

Mandatory

Type

Location

Description

value

Yes

Integer

Path

Terminal status.

  • 0: enabled.
  • 1: disabled.

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.

[Array element]

Yes

Array of strings

Body

List of terminal SNs. If the terminal status corresponding to an SN is the same as that in the record, the status of the terminal is not changed.

maxLength: 100

minLength: 1

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

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

["asdasfscasd"]

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: 702639ba08cda213b2699300e7f166e8

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 PUT -H 'X-Access-Token: stbVbWSIgzfOQ8JnbmPIoBIR3ig8xnVScQOF' -d '["asdasfscasd"]' https://api.meeting.huaweicloud.com/v1/usg/dcs/corp/device/status/0
Parent topic: Hard Terminal Management