Legacy API End-of-Life Announcement - RingOut.asp, FaxOut.asp

  • 1
  • Announcement
  • Updated 2 weeks ago
  • (Edited)
We introduced our full-featured REST APIs 3 years ago and it is time to deprecate our old RCP APIs now. The REST APIs have much more capability, coverage and security. The "ringout.asp" and "faxout.asp" API endpoints will be discontinued and cease to function with our 10.2 release, currently targeted for August 1, 2018. Please read below on what you will get with our REST APIs and how to upgrade your apps.

Which APIs are being depreciated?

RingOut.asp

FaxOut.asp


What will you get with our new REST API?

Both RingOut and FaxOut have been enhanced. With RingOut, you can get presence notifications so your app is immediately aware of call status including ringing and connection. You can also move beyond RingOut to initiate and receive calls directly within your browser via WebRTC. With FaxOut, you can get final fax disposition status including successful sends failure reasons, e.g. number is busy. There are many more features and over 100 API endpoints including managing your account, retrieving call log and message store data, and building endpoints using our Embeddable Voice web widget and React component library. You can read more about these on our Developer Portal and our API Reference:


How can I upgrade my app?

Follow our Developer Guide intstructions here:


If you have any questions on upgrading your app, please join us on our real-time chat support group using Glip here:

Photo of John Wang

John Wang, Official Rep

  • 5,496 Points 5k badge 2x thumb

Posted 5 months ago

  • 1
Photo of Brian Kleinfall

Brian Kleinfall

  • 220 Points 100 badge 2x thumb
The old API is 100X simpler - the new API sucks - way over complicated things.  Not going to spend hours and hours trying to get this thing to work.  It would be easier to change phone services.