HTTP POST - xml
This transaction type allows customers to specify their own XML data, not following a SOAP convention, but instead a simpler protocol of the customer's own choosing. Concord does not specify what may be contained in that XML file but allows anything form the specified token list.
HttpContentType - xml
text/xml
Http Header Template setting
The Http Header Template setting provides the URL that notifications should be posted to. The template should be provided to Concord Customer Service before this method can be used.
Examples URL's:
Format: {protocol}://{server}/{page}
Note
{protocol} : http or https
{server} : server address to post notification to
{page} : page to post form data to. Can be ommitted if url does not have a page name
https://yourserver.com/faxnotify.aspx
https://yourserver.com/faxnotify.htm
https://yourserver.com/faxnotify/
https://yourserver.com/faxnotify
![]() |
---|
For security reasons we strongly recommend to use the Https protocol. |
Http Body Template setting
text/xml
List of available Http Notification Tokens
Xml | ![]() |
---|---|
<?xml version=1.0” encoding=utf-8”?> <faxDetails> <AuthUser>%{AuthUser}</AuthUser> <AuthPassword>%{AuthPassword}</AuthPassword> <Account>%{Account}</Account> <CalledNumber>%{CalledNumber}</CalledNumber> <CallerNumber>%{CallerNumber}</CallerNumber> <FaxReceiveDateTime>%{FaxReceiveDateTime}</FaxReceiveDateTime> <FaxDuration>%{FaxDuration}</FaxDuration> <FaxPartialFlag>%{FaxPartialFlag}</FaxPartialFlag> <FaxPages>%{FaxPages}</FaxPages> <FaxSpeed>%{FaxSpeed}</FaxSpeed> <FaxFormat>%{FaxFormat}</FaxFormat> <FaxMessageId>%{FaxMessageId}</FaxMessageId> <FaxResolution>%{FaxResolution}</FaxResolution> <FaxSenderCSID>%{FaxSenderCSID}</FaxSenderCSID> <FaxRecipientTimeZone>%{FaxRecipientTimeZone}</FaxRecipientTimeZone> <FaxFiles>%{FaxFiles}</FaxFiles> </faxDetails> |
Token %{FaxFiles} will be expanded into a list of the following XML
Xml | ![]() |
---|---|
<FaxFile> <FileName>string</FileName> <FileData>base64Binary</FileData> </FaxFile> |