Difference between revisions of "API Method MessageCompose"
From Updox API
Line 11: | Line 11: | ||
− | == Request and Response JSON | + | == Request and Response JSON == |
Sending this transaction consists of the following request JSON and response JSON and returns a token: | Sending this transaction consists of the following request JSON and response JSON and returns a token: | ||
[[File:MessageCompose3.png]] | [[File:MessageCompose3.png]] | ||
Line 29: | Line 29: | ||
Browsing to this url will show the following '''''one-use-only''''' Direct message compose screen: | Browsing to this url will show the following '''''one-use-only''''' Direct message compose screen: | ||
[[File:MessageCompose4.png]] | [[File:MessageCompose4.png]] | ||
+ | |||
+ | When the user hits Submit, this window will execute an API call behind the scenes. |
Revision as of 16:46, 8 April 2014
Contents |
Credentials
Provide appropriate credentials for the user who will be sending the message:
Attachments, Prepopulation, Metadata
Provide any relevant additional parameters. If an attachment is to be sent, it must be specified here:
Request and Response JSON
Sending this transaction consists of the following request JSON and response JSON and returns a token:
Build URL
Use this token to construct a url in the following manner: https://{environment}/sso/messageCompose/{vendorId}/{token}
which for this example would look like this: https://updoxqa.com/sso/messageCompose/updox/611e840357c9dd58625436996cc2631910188c61
Compose Message
Browsing to this url will show the following one-use-only Direct message compose screen:
When the user hits Submit, this window will execute an API call behind the scenes.