part of #1545
Both endpoints accept Authorization header Bearer: IDTOKEN
grabbing a reply token before uploading a message
POST https://fes.<domain>/api/v1/message/new-reply-token
response (json):
data classMessageReplyTokenResponse(
valreplyToken:String
)
uploading message to web portal
POST https://fes.<domain>/api/v1/message
The content of the POST are a http multipart request with fields:
| multipart name | type | structure |
| details | application/json | see below |
| content | application/octet-stream | bytes |
request details structure (json)
data classMessageUploadRequest(
valassociateReplyToken:String, // the value you received when calling the first endpointvalfrom:String, // sender emailvalto:List<String>, // who message will be sent tovalcc:List<String> = emptyList(), // same, ccvalbcc:List<String> = emptyList() // same, bcc
)
response structure (json)
data classMessageUploadResponse(
valurl:String
)
With the above info you should be able to successfully make a request to upload a message to web portal. You will get back URL, which if you follow, should exist.
part of #1545
Both endpoints accept
AuthorizationheaderBearer: IDTOKENgrabbing a reply token before uploading a message
POST https://fes.<domain>/api/v1/message/new-reply-tokenresponse (json):
uploading message to web portal
POST https://fes.<domain>/api/v1/messageThe content of the POST are a http multipart request with fields:
| multipart name | type | structure |
|
details|application/json| see below ||
content|application/octet-stream| bytes |request details structure (json)
response structure (json)
With the above info you should be able to successfully make a request to upload a message to web portal. You will get back URL, which if you follow, should exist.