What changes will the new system bring to the sipgate REST API and sipgate.io?

Changes to the sipgate REST API and sipgate.io with the new sipgate neo system, including history, push API, RTCM, and channels.

In September 2025, sipgate released a new system for end customers. All accounts created since September 2025 already run on this new system, while older accounts that existed before September 2025 will be migrated gradually. The change also affects the behavior of the sipgate REST API and sipgate.io. All changes affecting the REST API and sipgate.io are described in detail in the following article

History

Events such as faxes and text messages can be viewed by new customers in the web interface and remain accessible via the history endpoints. Call events will no longer be available via these endpoints in the future; a request will return an empty result. Instead, call events, both incoming and outgoing, will be stored in the channel and offered via the channel endpoints, which are still under construction. Follow the implementation at https://feedback.sipgate.de/ (only in german available) and feel free to add any missing requirements as feature requests.

For migrated existing customers with a sipgate Neo account, call events will also be written to the usual event list in the web interface and will therefore continue to be available via the previous history endpoints for the time being.

Push API

The Push API has been expanded for sipgate Neo and now supports incoming and outgoing channel calls. Webhook configuration continues to be carried out in the Appweb. There you can specify for which channels webhooks should be triggered.

RTCM - Real Time Call Manipulation

The RTCM endpoints are functionally expanded in the backend so that the new channel calls can still be controlled with the existing endpoints. The response structure remains unchanged for compatibility purposes.

Channels

Channels replace groups and the previously known personal routings (phone lines).

With sipgate Neo, phone calls are always linked to a channel. The following endpoints are currently available to derive this reference:

End point (api.sipgate.com/v2)	Description
GET /channels	Retrieve the channels of an account.
GET /channels/{channelId}/events	Retrieve the call events of a channel. Only authorized users (channel members or admins for non-private channels) can access the events. To navigate through larger event sets, use the position parameter: The initial request returns the first events and a position value. Pass this position value in the next request to retrieve the next page. The position marks the starting point ("start after")--the event with this key is not returned again.
PUT /channels/{channelId}/users	Set the user list for a channel.
PUT /channels/{channelId}/users/{userId}/devices	Set the list of devices for a user with which they should be represented in the channel.
PUT /channels/{channelId}/name	Set the name of a channel.
DELETE /channels/{channelId}	Delete a channel.