dxp-ux

[POST]

communicationMessage (TMF681): This use case creates a communication entity for SMS and Email for PayTM

/communicationMessage:

Key Considerations for PR:

1. The Paytm team will manage email and SMS templates.
2. We are assuming that there won't be a large payload for P0 notifications and attachment.
3. Both application/json & application/zip request payload is supported.
4. P0 notifications will be customer-specific and will be sent one at a time.

"SMS"

1. For "SMS", the message is sent from Mavenir.
2. Mavenir doesn't accept special characters in "content" field (Example: á, é, ñ).
3. Mavenir will send SMS to only one reciever.phonenumber at a time.
4. Mavenir will send SMS with the same name sent from input request field "sender.name". If we wont receive sender.name from input request, ESB will send default value as "Liberty".
5. There is no format and length validation on reciever.phoneNumber in ESB.
6. Mavenir doesn't accept spaces and special characters in case of Phone Number, expected phoneNumber format "1++"countryCode"++PhoneNumber". Example: 1787XXXXXX.

"Email"

1. For "Email", ESB is integrated with AWS SES Service.
2. Sender email(from email address) should configured in AWS SES, same configured email should be passed. Example: For eCommerce LCPR "shop-noreply@libertypr.com" is configured.
3. The payload.content type should be "JSON" string.

/communicationMessage/send:

URL

https://[localhost]:[port]/ecom-ux/v1/CR/communicationMessage/send

Base URI Parameter

Headers

Security Headers

QueryParams

Data Model: CR B2B