This API is used to get the content of the deployment based on TransactionID for SMS and USSD channels. You can get the TransactionID from the Get Last "N" Customer Transactions API.
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.
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 |
|---|---|---|---|
| transaction-id | String | Yes | Specifies the transaction ID. |
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. |
| msg | Returns the actual message sent in case of success. |
Request Example
https://<yourdomain>/campaignapi/resources/v3/campaigncontents/123456789
Response Codes
The API will return a code within the response as per the following table in case of failure scenarios.
| HTTP Status Code | Code within API Response | Description |
|---|---|---|
| 401 | 430 | Authorization failed. This resource is not allowed to access using this TOKEN or KEY |
| 401 | 498 | Invalid token or Access token expired |
| 404 | 404 | Request failed. Check the exact reason of failure in application code and description of error stream. |
| 405 | 405 | Method not supported |
| 429 | 429 | Too many requests. Throttle limit reached for the time window. |
| 500 | 500 | Internal server error |
| 500 | 1002 | Mandatory field missing |