# Introduction

## What can you do with the Apizee REST APIs?

REST APIs split into 2 categories:

| ApiRTC APIs                                                                                                                                                                                 | Apizee APIs                                                                                                                                                                                                                |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Linked to ApiRTC platform                                                                                                                                                                   | Linked to the Apizee platform                                                                                                                                                                                              |
| Manage low level communication objects                                                                                                                                                      | Manage Apizee SaaS solutions objects                                                                                                                                                                                       |
| <p>Available endpoints:</p><ul><li><code>/sessions</code></li><li><code>/conversations</code></li><li><code>/sms</code></li><li><code>/emails</code></li><li><code>/medias</code></li></ul> | <p>Available endpoints:</p><ul><li><code>/users</code></li><li><code>/enterprises</code></li><li><code>/service</code></li><li><code>/tickets</code></li><li><code>/conferences</code></li><li><code>/hl7</code></li></ul> |

Authentication is managed by a shared endpoint: `/authentication`

\>> [Try it now](https://cloud.apirtc.com/sdk/api/)

\>> [Get the specs](https://cloud.apirtc.com/sdk/api/)

## Authentication

You need to be an Apizee or ApiRTC authenticated user to use the APIs.

| Platform                                  | Access to ApiRTC APIs | Access to Apizee APIs |
| ----------------------------------------- | :-------------------: | :-------------------: |
| Account on <https://cloud.**apirtc**.com> |                       |           x           |
| Account on <https://cloud.**apizee**.com> |           x           |           x           |

:point\_right:Create an account on the [ApiRTC Console](https://cloud.apirtc.com/register) or on the [Apizee plaform](https://cloud.apizee.com) depending on what endpoint you need.

:point\_right:Use the `/authentication` endpoint providing your username and password to get a token in return (see [Bearer Authentication](https://swagger.io/docs/specification/authentication/bearer-authentication/)).

{% hint style="warning" %}
Be mindful that you get the authentication token by passing clear username and password along with your API call; this operation must be done by your application's backend to avoid security issues and NOT by your frontend part.
{% endhint %}

:point\_right:Include the token in the `Authorization` header of requests:

```
Authorization: Bearer <token>
```

Example of use:

```bash
curl -X 'POST' 'https://cloud.apizee.com/api/token?grant_type=password&username=test%40apizee.com&password=xxYY1122' 
    -H 'accept: application/JSON' 
    -d 
```

Response

```json
{
    "access_token": "xyzaaa-c900-4dd2-8192-12345678",
    "created_at": "2023-07-12T15:22:04+00:00",
    "expires_in": 86400
}
```

{% hint style="info" %}
[Read more about the Bearer Authentication](https://swagger.io/docs/specification/authentication/bearer-authentication/)
{% endhint %}

## Compliant with the OpenAPI Standards

ApiRTC APIs are compliant with the OpenAPI Standards.<img src="/files/Opqf7oJopwYdtZmpvRUh" alt="" data-size="original">

## Webhooks

Design a two-way integration by enabling ApiRTC to push events to your systems.

:point\_right: [Read more about Webhooks](/apirtc-developer-portal/rest-apis-and-integration/webhooks.md)


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev.apirtc.com/apirtc-developer-portal/rest-apis-and-integration/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.