Issue with Callback endpoint
There seems to be a bug based on your documentation:
"When the callback URL is set via either of these methods, OpenText messaging service will POST the final fax status as application/json to this end point. The schema is the same as in the response from "Get fax status" method except that the values of "job_state" parameter will not include "complete" even if all deliveries are complete."
However, when calling the "https://api.us.cloudmessaging.opentext.com - Production North America", the result that is returned is in XML (SOAP).
Using the exact same body when sending the fax but calling the "https://t2api.us.cloudmessaging.opentext.com - Pre-production" endpoint, the callback returns in JSON.
How can this be fixed so that the callback is in JSON using the same "Get fax status" schema?
Comments
-
We advise you to use JSON. However, we are also looking at getting XML document.
If this is an emergency, please raise a support ticket.
0 -
Hi Arun,
We've created a ticket and they told us to go to the forum. We also would like to use JSON instead of XML, however there is no way for us to update the user profile without contact you. When we've contacted you to make the update, they redirected us here because the update of the status still did not make calls in JSON.
1
Categories
- All Categories
- 122 Developer Announcements
- 53 Articles
- 150 General Questions
- 147 Thrust Services
- 56 OpenText Hackathon
- 35 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 917 Cloud Fax and Notifications
- 84 Digital Asset Management
- 9.4K Documentum
- 31 eDOCS
- 181 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 8 XM Fax
- Follow Categories
