Communicate Webmail is an accessible, secure web interface that allows users to interact with other Direct messaging users without deploying integration or physical infrastructure. Users can access their Direct messages from any device with internet access. Communicate Webmail encrypts and decrypts the data.
Communicate Webmail provides a REST messaging API. Users can send and receive messages securely over the Direct network using this API.
The current frozen version of the Communicate Webmail API is 3.5. The API interfaces are stable and guaranteed to stay as such until this version is retired.
The Communicate Webmail API is versioned through the Accept
and Content-Type
headers, which specify the version of the object to retrieve. For example, version 3.5 of the API is retrieved by requesting the application/vnd.orchestral.Webmail.3_5+json
media type. In all cases, application/json
is treated as the latest version of the API.
The URIs for the Communicate Webmail REST API have the following structure:
https://{environment}/actor/current/webmail/DIRECT/mailboxes/resource
For example, https://{environment}/actor/current/webmail/DIRECT/mailboxes/{mailboxAddress}/preferences
Our cheat sheet uses the following conventions:
HTTP verb /Resource URI
property
POST /{mailboxAddress}/preferences/autoForward
orPUT /{mailboxAddress}/preferences
autoForwardOn
autoForwardGroup
POST /{mailboxAddress}/preferences/autoReply
orPUT /{mailboxAddress}/preferences
autoReplyOn
autoReplyMessage
POST /{mailboxAddress}/preferences/mailboxSharing
(if you know the Direct email address of the user you want to share your mailbox with) orPUT /{mailboxAddress}/preferences
sharedMailboxOn
sharedUsers
To associate the contact with a contact group, you require the unique identifier of the contact group. (contactGroupId
).
To add a contact to the contact group, you require the unique identifier of the contact (contactId
).
The Communicate Webmail API returns standard HTTP response codes.
Code | Status | Description |
---|---|---|
200 | OK | Your request was successfully received, understood and accepted. |
201 | Created | Your request has resulted in a new resource being created. |
204 | No content | Your request was successfully processed, and there is no additional content to send in the body of the response. |
400 | Bad request | Your request was invalid. A parameter, or the data in a parameter, may be incorrect. |
401 | Unauthorized | Your API key or access token has expired or is invalid. |
404 | Not found | The requested resource cannot be found. Please ensure that this resource exists. |
409 | Conflict | Your request cannot be completed due to a conflict with another rule. |
413 | Payload too large | Your request payload is larger than the server is willing or able to process. |