We have re-coded these Web services in our new (MyRapidi) framework with the goal to make them as compatible as possible with the old ones and tested them accordingly. You might however need to reload the WSDL and compile your client code again, in order to make it work.
For the SFDCScheduleTrigger used from Salesforce, we have tested that these continue to work without any modification on your part.
The existing address api.rapidionline.com is now pointing to the new server. In addition, we also have api.myrapidi.com pointing to the new server. Both can/should be used with SSL.
In order to help you in a transition period, we will keep the old API interface running on the address app.rapidionline.com for a few months more. Please let us know if you continue to use the old address and when you plan to migrate to the new.
New REST API in development
We are working on a new REST-based API that will expose the above functions (ScheduleTrigger and ScheduleStatus) and in addition, also give you access to many other parts of the MyRapidi interface in a programmatic way. For Example, access to read and search Log entries. Stay tuned for more information on this!
As always don't hesitate to contact us if you have any questions
About the author
Michael founded Rapidi on technological excellence, fantastic customer service and continuous improvement. A data integration specialist since 1987, he remains focused on creating technology that solves real business problems.