> 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/parallels-client-url-scheme/url-format.md).

# URL Format

A URL string always begins with the Parallels Client URL scheme. See the table in the previous section for a scheme supported on a specific platform. If both URL schemes are supported, you can use either one.

The first parameter that you include after the URL scheme is the `Command` parameter. It tells Parallels Client what kind of action should be performed. The available commands are:

* **GetVersion** — Allows to determine on the web server side which Parallels Client version is installed on a user device, or if the Parallels Client is installed at all.
* **LaunchApp** — Creates a connection, authenticates a user, launches a published resource.
* **Get2xa** — Performs the same actions as the LaunchApp command (above), but uses advanced security, which eliminates passing sensitive information (server name, user credentials, published resource info) in the URL itself.
* **LogOff** — Logs off the user from a session on a specified server or from all sessions on all servers.

The `Command` parameter is placed in the URL as shown in the following example:

`tuxclient:///?Command=LaunchApp`

Command options are specified after the command using the ampersand ("&") separator:

`tuxclient:///?Command=LaunchApp&AppID=2360&ConnMode=0 ...`

Note that the `prlclient://` URL scheme uses the same exact format demonstrated here and in all other examples included in this 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-client-integration-guide/parallels-client-url-scheme/url-format.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.