> 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-client-integration-guide/ras-web-client-api.md).

# RAS Web Client API

This chapter describes how to integrate a third-party web portal with the RAS Web Client ([User Portal](https://docs.parallels.com/landing/ras-user-portal-guide/)) to authenticate users and launch published resources.

There are two integration methods:

* **Authentication Handoff API** (current). Your integration POSTs a JSON payload with the user's credentials to the RAS Secure Gateway, which responds with a redirect to the User Portal. This is the supported method for all new integrations. See [**Authentication Handoff API**](/landing/ras-client-integration-guide/ras-web-client-api/authentication-handoff-api.md).
* **Legacy Web Client API** (deprecated) launch data is passed through a JavaScript payload URL (?appinfo=...). This method is deprecated and is disabled by default starting with Parallels RAS 21.2.

{% hint style="warning" %}
**Attention**: The legacy Web Client API (appinfo payload) is deprecated for security reasons. When you upgrade to Parallels RAS 21.2 or later, it is disabled by default. Existing integrations must migrate to the Authentication Handoff API. See [**Migrating from the Legacy Web Client API**](/landing/ras-client-integration-guide/ras-web-client-api/migrating-from-the-legacy-web-client-api.md).
{% endhint %}


---

# 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://docs.parallels.com/landing/ras-client-integration-guide/ras-web-client-api.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.