> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/using-finder-classic/monitoring-it-services-classic/specifying-url-paths-of-web-based-services-classic.md).

# Specifying URL paths of web-based services (classic)

{% hint style="info" %}
Nexthink Finder is a Windows-only desktop application whose functionality is now available within the Nexthink web interface. Nexthink can now be used directly from a browser and most functions no longer require an additional desktop application.
{% endhint %}

You can define services in Nexthink for measuring the connectivity of employees to web applications and websites by stating the domain name of the particular provider of the service. In some cases, you may want to differentiate several services that lie within the same domain. For instance, you may want to highlight the difference between:

* `www.example.com/agenda`
* `www.example.com/share`

To treat these two addresses as different services, you must first [configure your Collectors to report the URLs](/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/reporting-the-url-of-http-web-requests-classic.md) of the web requests addressed to the domain `www.example.com.`

Then [create two services](/user-guide/using-finder-classic/monitoring-it-services-classic/creating-a-service-with-finder-classic.md) in Finder of the type **HTTP web requests with URL path**. In addition to the domain name, you can specify a URL path to distinguish services within the same domain. Note that the URL path option is only available for HTTP and not for TLS web-based services. Continuing with our example, you would specify as URL paths:

* agenda
* share

All subpaths are naturally included in the definition. You may also use the star pattern to substitute for zero or more characters in the URL path.

| Domain            | URL path | Matches                                                                                                                                                                                                                   |
| ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `www.example.com` | agenda   | <ul><li><code>[www.example.com/agenda/mycal.php](http://www.example.com/agenda/mycal.php)</code></li></ul>                                                                                                                |
|                   | share    | <ul><li><code>[www.example.com/share/myshare.html](http://www.example.com/share/myshare.html)</code></li><li><code>[www.example.com/share/groupshare.html](http://www.example.com/share/groupshare.html)</code></li></ul> |
|                   | sh\*     | <ul><li><code>[www.example.com/share/myshare.html](http://www.example.com/share/myshare.html)</code></li><li><code>[www.example.com/sharing/index.html](http://www.example.com/sharing/index.html)</code></li></ul>       |


---

# 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.nexthink.com/user-guide/using-finder-classic/monitoring-it-services-classic/specifying-url-paths-of-web-based-services-classic.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.