> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-connection-broker/enabling-connection-broker-api.md).

# Enabling Connection Broker API

It is possible to manage sessions in Parallels RAS without using the RAS Connection Brokers to carry out the management. This is useful for organisations that wish to manage sessions via a third-party method. The steps to enable this are below.

In addition to the steps below, configuration via API is needed. This API is documented [here](https://download.parallels.com/ras/v21/en_US/Parallels-RAS-Connecting-Using-Connection-Broker-API.pdf).

Navigate to **Farm** > **Site** > **Connection Brokers** and follow the instructions below:

1. Choose **Tasks** > **Site Defaults** (or choose the properties of an individual Connection Broker to assign to a specific Connection Broker)
2. Choose the **API** tab
3. Choose **Enable API** (if configuring on an individual Connection Broker, you will need to deselect **Inherit Default Settings**)

### **SSL/TLS**

1. Select the **API Port** option and specify a port number for secure API communication
2. In the **Accepted SSL Versions** drop-down list, select the SSL/TLS version required.
3. In the **Cipher Strength** field, select a desired cipher strength.
4. If Custom is chosen in the **Cipher Strength** field, in the **Cipher** field, specify the cipher. A stronger cipher allows for stronger encryption, which increases the effort needed to break it.
5. The **Use ciphers according to server preference** option is ON by default. You can use client preferences by disabling this option.
6. In the **Certificates** drop-down list, select a desired certificate. For the information on how to create a new certificate and make it appear in this list, see the [**SSL Certificate Management** ](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ssl-certificate-management.md)chapter.

### **API Token**

To use an API token, set the HTTP Authorization header value set when making API requests.

When the **Enable API** option is selected, an **API Token String** is generated. Choosing **Regenerate** will issue a new API Token String.

### **Encryption Certificate**

The chosen encryption certificate will be used by the Connection Broker API when creating runtime data between backend components.

To set this, navigate to **Farm** > **Site** > **Connection Brokers** and select the **API** tab (if this tab is not visible, it indicates that **Enable API** has not been selected).

If **Automatic** is selected, the default method of using the site certificate will be used. The list shows certificates available with the `Third-Party Encryption` property selected.

For the information on how to create a new certificate and make it appear in this list, see the [**SSL Certificate Management** ](/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ssl-certificate-management.md)chapter.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.parallels.com/landing/ras-admin-guide/parallels-ras-21-administrators-guide/ras-connection-broker/enabling-connection-broker-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.