The ECM REST APIs allow to configure campaigns, strategies and insert contacts to a campaign. It currently supports the following functions:
...
Protocol | HTTP or HTTPS |
---|---|
URL | https://<UMM-FQDN>/umm/ecm/campaign/delete?id=1 |
Authorization | Bearer token-from-login-API |
Content-Type | Application/JSON |
HTTP Method | DELETE |
Input/Output Format | JSON |
Request Parameters |
|
HTTP Request | |
HTTP Response | 200: Success 404: Not found 500: Internal Server Error 503: Service Unavailable |
Example Response |
...
Protocol | HTTP or HTTPS | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
URL | https://<UMM-FQDN>/umm/ecm/callStrategyAttempt/save | ||||||||||||
Authorizaitoion | Bearer token-from-login-API | ||||||||||||
Content-Type | Application/JSON | ||||||||||||
HTTP Method | POST | ||||||||||||
Input/Output Format | JSON | ||||||||||||
Request Body |
If the call result is one of the above, it allows to define which attempt should be made and after how much time. Example: This means if call_result = BUSY then go for attempt 2 and execute it after 30 minutes but if call_result is NO_ANSWER, close the record. In the case of an SMS attempt, it allows defining what to do if there's no reply from the customer, ; i.e. whether the system should make another attempt or close the contact. Example: | ||||||||||||
HTTP Request |
| ||||||||||||
HTTP Response | 200: Success 404: Not found 500: Internal Server Error 503: Service Unavailable | ||||||||||||
Example Response |
|
...