> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/connections-and-integrations/api/was-ist-die-sipgate-api-und-welche-funktionen-bietet-sie.md).

# What is the sipgate API and what functions does it offer?

Overview of the sipgate API - control functions such as calls, SMS, fax, voicemails, and event lists via the interface.

{% hint style="info" %}
**Note:** This feature is available only to customers on **sipgate classic** The feature is integrated in a different form in sipgate neo.
{% endhint %}

The sipgate API (Application Programming Interface) provides the **functionality** of the sipgate platform **to external applications** The sipgate API offers features in the following areas:

* Making phone calls
* Sending SMS messages
* Sending and receiving faxes
* Retrieving account balance information
* Accessing the event list (data on calls, faxes, voicemails, and SMS messages)
* Accessing voicemails
* Provisioning data for VoIP endpoints

In general, information such as sender, recipient, and timestamp is available for all items in the event list. In addition, for **voicemail, fax, and SMS** the contents can, for example, be downloaded as files.

All information about the sipgate API is compiled and documented in detail on the [sipgate.io](https://www.sipgate.io) website.

**Who should I contact if I have problems with the sipgate API?**

For questions about the REST API and the sipgate.io Push API, contact our developer team directly. You can reach us

* by email at <tech@sipgate.io>

We have set up a [**mailing list**](http://groups.google.com/group/sipgate-api) as a discussion platform for developers, which you can subscribe to.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sipgate.de/cloud-telefonanlage/en/connections-and-integrations/api/was-ist-die-sipgate-api-und-welche-funktionen-bietet-sie.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
