This section provides a reference for APIs that should be implemented by this Building Block.
Request successfully accepted
Request successfully accepted. Use \"requestUid\" to track it's status.UfQK-CPju-Ea5B-6y7X-8A72-VqU5Invalid input
When sending batch emails, recipients information is passed in base64 format. Sender information and email content must be the same for all recipients.
Request successfully accepted
Request successfully accepted. Use \"requestUid\" to track it's status.UfQK-CPju-Ea5B-6y7X-8A72-VqU5Invalid input
This service may reside on both Messaging BB's and client's side. If used, a matching OpenAPI spec must be provided by the service provider, describing the expected input when making request to the endpoint.
Request successfully accepted
No content
Invalid input
No content
Get status of sent emails. Use both "apiKey" and "requestUid" in your request.
Request successfully accepted
01004025709032Invalid input
POST /send/email/single?body=[object+Object] HTTP/1.1
apiKey: text
Accept: */*
{
"response": "Request successfully accepted. Use \\\"requestUid\\\" to track it's status.",
"requestUid": "UfQK-CPju-Ea5B-6y7X-8A72-VqU5"
}POST /send/email/batch?body=[object+Object] HTTP/1.1
apiKey: text
Content-Type: application/json
Accept: */*
Content-Length: 6
"text"{
"response": "Request successfully accepted. Use \\\"requestUid\\\" to track it's status.",
"requestUid": "UfQK-CPju-Ea5B-6y7X-8A72-VqU5"
}POST /callback/email?body=[object+Object] HTTP/1.1
apiKey: text
requestUid: text
Accept: */*
GET /status/email?status=scheduled HTTP/1.1
apiKey: text
requestUid: text
Accept: */*
{
"scheduled": 0,
"processing": 1004,
"deferred": 0,
"bounced": 257,
"notSent": 0,
"delivered": 9032
}