post https://yourdomain.webexcampaign.io/campaignapi/resources/v3/delete
This API is used to delete profiles.
Know your endpoint
Based on the domain you use to log in to Webex Campaign, the endpoint domain for your API varies. For more information, refer to the Know Your API Endpoints section.
Go to the Postman Collection section to learn how to import a Postman collection. Click the below button, If you already know how to import a postman collection.
Request Headers
The following table describes the request headers:
| Request Header | Description |
|---|---|
| content-Type | application/json |
| authorization | Access token or API Secret Key in Bearer format Example: Bearer $(key) |
Body Parameters
The following table describes the elements in the request body:
| Parameter | Type | Mandatory | Description |
|---|---|---|---|
| profile-name | String | No | Specifies the Profile Name. |
| key | String | Yes | Specifies the profile primary key. |
| exparam1 | String | No | Specifies the extra parameters that can be passed for audit logging purpose. You can pass up to 10 extra parameters. |
Request Example
{
"profile-name":"sampleprofile",
"key":"9463183918",
"exparam1":"val1"
}
Response Parameters
This API will return the following response parameters:
| Parameter | Description |
|---|---|
| code | Returns the response code in case of failure. |
| description | Returns the description of the response in case of failure. |
| transaction-id | Returns the unique Transaction ID of the operation in case of success. |
Failure Response Codes
The API will return code within the response as per the following table in case of failure scenarios.
| HTTP Status Code | Code within API Response | Description |
|---|---|---|
| 200 | 102 | Invalid profile id |
| 200 | 1010 | The request was not processed. |
| 200 | 1020 | Contact profile not found |
| 401 | 430 | Authorization failed. This resource is not allowed to access using this TOKEN or KEY |
| 401 | 498 | Invalid token or Access token expired |
| 405 | 405 | Method not supported |
| 429 | 429 | Too many requests. Throttle limit reached for the time window. |
| 499 | 499 | Request failed. Check the exact reason of failure in application code and description of error stream. |
| 500 | 500 | Internal server error |
| 500 | 1001 | Invalid input JSON |