Allocating Enterprise Resources as an SP Administrator
Description
This API is used to allocate new enterprise resources. This API can also be used to modify allocated enterprise resources. If resourceId is carried in the request, the system determines whether the resource exists. If the resource exists, the system modifies the resource. (For details about parameters that can be modified, see the API for modifying enterprise resources.) Otherwise, the system adds the resource.
Debugging
You can debug this API in API Explorer.
Prototype
Request Method |
POST |
---|---|
Request Address |
/v1/usg/dcs/sp/corp/{corp_id}/resource |
Transport Protocol |
HTTPS |
Request Parameters
Parameter |
Mandatory |
Type |
Location |
Description |
---|---|---|---|---|
corp_id |
Yes |
String |
Path |
Enterprise ID. |
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 ResourceDTO objects |
Body |
List of resources to be added. The list can contain up to 100 resources. |
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/sp/corp/818803911/resource Connection: keep-alive X-Access-Token: stbvmKo5lr6vT7QIzKHg4iqicUBcYMb3qlki Content-Type: application/json Content-Length: 31 Host: api.meeting.huaweicloud.com User-Agent: Apache-HttpClient/4.5.3 (Java/1.8.0_191) [ { "count": 10, "expireDate": 2549030400000, "type": "VMR", "typeId": "ff808081699b56cb0169c411a0980152" } ]
Example Response
HTTP/1.1 200 Date: Tue, 17 Dec 2019 09:32:47 GMT Connection: keep-alive Pragma: No-cache Cache-Control: no-cache Server: api-gateway X-Request-Id: 539e8b710378987ffc5eb844b5e5c290
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: stbvmKo5lr6vT7QIzKHg4iqicUBcYMb3qlki' -d '[{"count": 10,"expireDate": 2549030400000,"id": "733ff391f2a14360af3b93bd1325f9f9","type": "VMR","typeId": "ff808081699b56cb0169c411a0980152"}]' https://api.meeting.huaweicloud.com/v1/usg/dcs/sp/corp/818803911/resource
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot