ImportCustomCallTagging

更新时间:
复制 MD 格式

You can invoke ImportCustomCallTagging to import multiple inbound number tags into a specified instance.

Note

This API has been deprecated. We recommend migrating to CCC(2020-07-01) - ImportCustomCallTaggings for enhanced functionality and continued support. While the deprecated API remains temporarily accessible, no further updates or bug fixes will be provided.

Try it now

Try this API in OpenAPI Explorer, no manual signing needed. Successful calls auto-generate SDK code matching your parameters. Download it with built-in credential security for local usage.

Test

RAM authorization

No authorization for this operation. If you encounter issues with this operation, contact technical support.

Request parameters

Parameter

Type

Required

Description

Example

InstanceId

string

Yes

The instance ID.

ccc-test

FilePath

string

Yes

The ObjectKey of the OSS object that contains the inbound number mark file. OSS is configured with the public customer storage bucket for Cloud Call Center. You can upload the inbound number mark file to this public customer storage bucket through the inbound management page of Cloud Call Center. After the upload succeeds, invoking this API reads the file content from OSS and imports it in batch. We do not recommend directly invoking this API. Instead, you can perform this operation through the default public cloud CRM System provided by Cloud Call Center.

temp/ImportCustomCallTagging.xlsx

Response elements

Element

Type

Description

Example

object

Schema of Response

RequestId

string

The request ID.

BA03159C-E808-4FF1-B27E-A61B6E888D7F

HttpStatusCode

integer

The HTTP status code.

200

Code

string

The response code.

OK

Message

string

The response message.

Data

array<object>

The list of inbound number tags that failed to be created.

object

Information about an inbound number tag that failed to be created.

Item

string

The number of the inbound number tag that failed to be created.

1312121****

Reason

string

The reason why the inbound number tag creation failed.

Valid values:

  • CUSTOM_NUMBER_ILLEGAL :

    The input list contains numbers with invalid formats.

  • CUSTOM_NUMBER_DUPLICATED :

    The input list contains duplicate numbers.

  • CUSTOM_NUMBER_ALREADY_EXISTS :

    The input list contains number tags that have already been created.

  • CUSTOM_NUMBER_TAG_NOT_EXIST :

    The input list contains number tags that have not been created.

  • CUSTOM_NUMBER_INSERT_DUPLICATED :

    Duplicate entries existed when writing inbound number tags to the backend.

  • CUSTOM_NUMBER_TOO_MANY_TAGS :

    The input list contains numbers that exceed the maximum allowed number of tags.

CUSTOM_NUMBER_DUPLICATED

Examples

Success response

JSON format

{
  "RequestId": "BA03159C-E808-4FF1-B27E-A61B6E888D7F",
  "HttpStatusCode": 200,
  "Code": "OK",
  "Message": "无",
  "Data": [
    {
      "Item": "1312121****",
      "Reason": "CUSTOM_NUMBER_DUPLICATED"
    }
  ]
}

Error codes

HTTP status code

Error code

Error message

Description

400 Parameter.Blank The parameter %s must not be null or empty.
400 Parameter.InvalidFileContent The content or format of the file (%s) is invalid.
500 InternalService.OSS An internal OSS service error occurred. %s
500 InternalService.DB An internal DB service error occurred. %s
404 NotExists.RamId RAM user %s does not exist.
404 NotExists.UserResourceFileKey User resource file key %s does not exist.

See Error Codes for a complete list.

Release notes

See Release Notes for a complete list.