What is the difference between sipgate API and sipgate.io?
Learn the difference between the sipgate REST API and the Push API, as well as their use cases and costs.
Last updated
Learn the difference between the sipgate REST API and the Push API, as well as their use cases and costs.
The sipgate.io functions and integrations are based on two sipgate APIs (interfaces): one REST- and one Push API. We refer to both APIs as "sipgate.io".
The main difference between the two APIs is when information is transmitted:
In the REST API you make individual requests using your programs. This allows you, among other things, to trigger new calls, check credit, and much more. You can use the functionality of this API as a sipgate customer free of charge use.
In the Push API the initiative comes from the other direction, from the sipgate.io servers. The timing is not arbitrary, but whenever an event occurs – an incoming call, for example. The long-term use of this API is subject to a fee. More about sipgate.io pricing can be found here.
With sipgate.io, you can combine the functions of the two interfaces and further develop your telephony individually and automatically. More about the possibilities of sipgate.io can be found in this article or on the sipgate.io website.
Update from January 16, 2023
Last updated

