Querying Service Ticket CC
Function
Query the service ticket CC email addresses.
URI
GET /v2/servicerequest/carbon-copy-emails
Request Parameters
|
Parameter |
Mandatory |
Type |
Description |
|---|---|---|---|
|
X-Auth-Token |
Yes |
String |
Specifies the user token. It can be obtained by calling the IAM API (value of X-Subject-Token in the response header). Minimum length: 1 Maximum length: 5000 |
|
X-Language |
No |
String |
Specifies the language environment. The value is a common language description character string, for example, zh-cn. It is zh-cn by default. Some internationalization information, such as the service ticket type and name, is displayed based on the language environment. Minimum length: 1 Maximum length: 32 |
|
X-Time-Zone |
No |
String |
Specifies the time zone. The value is a common time zone description character string, for example, GMT+8. It is GMT+8 by default. Time-related data is processed based on the time zone of the environment. Minimum length: 1 Maximum length: 32 |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
cc_email_info |
IncidentOrderCCEmailInfoV2 object |
Indicates the information of the last CC email. |
|
mc_email_infos |
Array of strings |
Indicates the CC email information. Minimum length: 1 Maximum length: 32 |
|
Parameter |
Type |
Description |
|---|---|---|
|
user_id |
String |
Specifies the user ID. Minimum length: 0 Maximum length: 64 |
|
customer_id |
String |
Specifies the customer ID. Minimum length: 0 Maximum length: 64 |
|
cc_email |
String |
Indicates the email where the operation occurs. Minimum length: 0 Maximum length: 5000 |
Request Example
None
Response Example
Status code: 200
Response of status code 200
{
"cc_email_info" : [ {
"user_id" : "123",
"customer_id" : "123",
"cc_email" : "123"
} ],
"mc_email_infos" : [ "123", "456" ]
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
Response of status code 200 |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
