Help Center/ Cognitive Engagement Center/ API Reference/ Call Center Configuration Interface Reference/ Number Management/ Deleting the Binding Relationships Between Access Codes, Skill Queues, and IVR Flows (deleteCalledRoute)
Updated on 2023-09-27 GMT+08:00
View PDF
Share

Deleting the Binding Relationships Between Access Codes, Skill Queues, and IVR Flows (deleteCalledRoute)

Scenario

Delete the binding relationships between access codes, skill queues, and IVR flows.

Method

POST

URI

https://Domain name/apiaccess/rest/cc-management/v1/calledRoute/deleteCalledRoute. For example, the domain name is service.besclouds.com.

Request Description

Table 1 Request header parameters

No.

Parameter

Type

Mandatory or Not

Description

1

X-APP-Key

String

No

App key field, which is the user ID. Contact the operation personnel to obtain the app key.

2

Authorization

String

Yes

Authentication field. The format is Bearer {Value of AccessToken returned by the tokenByAkSk interface}. (A space is required after Bearer.)
Table 2 Request body parameters

No.

Parameter

Type

Mandatory or Not

Description

1.1

dnids

String

Yes

Configuration ID (dnid returned when the Called Route is queried). Use commas (,) to separate multiple IDs. A maximum of 1000 IDs can be deleted.

Response Description

  • Status code: 200
    Table 3 Response body parameters

    No.

    Parameter

    Type

    Mandatory or Not

    Description

    1.1

    returnCode

    String

    No

    Return code. The options are as follows: 0: success; other values: failure.

    1.2

    description

    String

    No

    Description.

    1.3

    data

    Object

    No

    Deletion result.

    1.3.1

    id

    String

    No

    ID of the deleted binding data record.

    1.3.2

    name

    String

    No

    Deleted binding data, which is in the accessCode+extCode format.

    1.3.3

    content

    String

    No

    Deleted access code.

    1. If all records are deleted successfully or fail to be deleted, the value of this parameter is the same as that of name.

    2. If the deletion is partially successful, the character string is as follows: Success:+Value of name+,Failed:+Value of name
  • Status code: 400

    Incorrect request. Check the request path and parameters.

  • Status code: 401

    Unauthorized operation. 1. Check whether you have purchased related services. 2. Contact customer service to check the status of your account.

  • Status code: 403

    Authentication fails.

  • Status code: 404

    The requested content is not found. Check the request path.

  • Status code: 500

    Business failure. Check the values of parameters in the request.

Error Codes

None

Example

Request header:

Content-Type:application/json
Authorization:Bearer XXXXXXXXXXXXXXXXXXXXXXX
X-APP-Key:XXXXXXXXXXXXXXXXXXXXXXX

Request parameters:

{
    "dnids": "1,2"
}

Response parameters:

{
    "returnCode": "0",
    "data": {
        "name": "9911411,99114111",
        "id": "1127983948544239618,1127986019188238339",
        "content": "9911411,99114111"
    },
    "description": "data delete success"
}
Parent topic: Number Management