SendTransactionalWithFallback

SendTransactionalWithFallback function sends transactional email, push and sms messages with fallback to recipients.

In case fallbackChannel parameter is not entered, only the specified channels will be sent.
In case fallbackChannel parameter is specified, the request for the entered value must be filled.

emailRequest (optional) : payload is like here.
pushRequest (optional) : payload is like here.
smsRequest (optional) : payload is like here.
fallbackChannel (optional) : values can be Email or Push or Sms.

Here are some scenario examples;

Scenario-1
Send email and push, if they are bounced send sms. In this scenario emailRequest, pushRequest and smsRequest should be filled and fallbackChannel specified as "Sms".


Scenario-2
Send email and sms, if they are bounced send push. In this scenario emailRequest, pushRequest and smsRequest should be filled and fallbackChannel specified as "Push".


Scenario-3
Send push, if there is bounced send sms. In this scenario pushRequest and smsRequest should be filled and fallbackChannel specified as Sms.


Scenario-4
Send push, if there is bounced send email. In this scenario pushRequest and emailRequest should be filled and fallbackChannel specified as "Email".


Scenario-5
Send sms, if there is bounced send email. In this scenario emailRequest and smsRequest should be filled and fallbackChannel specified as "Email".


Scenario-6
Send email, push and sms. In this scenario emailRequest, pushRequest and smsRequest should be filled and fallbackChannel should be empty.


Idempotency Support: This endpoint supports idempotency via the optional traceId parameter. For more information, see Rest API Idempotency.


Scenario-7
Send email and sms. In this scenario emailRequest and smsRequest should be filled and fallbackChannel should be empty.


Scenario-8
Send email. In this scenario emailRequest should be filled and fallbackChannel should be empty.


Scenario-9
Send push. In this scenario pushRequest should be filled and fallbackChannel should be empty.


Scenario-10
Send sms. In this scenario smsRequest should be filled and fallbackChannel should be empty.

Body Params
emailRequest
object

payload is like here.

string

values can be Email or Push or Sms.

pushRequest
object

payload is like here.

smsRequest
object

payload is like here.

Headers
string
required
Defaults to {$$.env.access_token}
string
enum
Defaults to application/json

Generated from available response content types

Responses

401

Not-authorized. Please re-login.

429

Too Many Requests

Language
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
Send Email
Send Email, Push with fallback Sms
Send Email, Push, Sms
Send Email, Sms
Send Email, Sms with fallback Push
Send Push
Send Push with fallback Email
Send Push with fallback Sms
Send Sms
Send Sms with fallback Email
FallbackChannelRequestCannotNull
InvalidFallbackChannel
TooManyRequest