> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/web-services-framework/web-services-endpoints.md).

# Web Services Endpoints

## Endpoints

The logicnets in the endpoints folder are the endpoints for your web service, and the web service calls endpoints by the name of the logicnet. You can organize your endpoints in folders, in which case you need to include the folder name in the path for the endpoint. For example, if your endpoint logicnet is called *function\_1*, the endpoint can be invoked by the following URL: https\:////function\_1 .

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-844da1839f5bc22c340098039174b87038043fdd%2Fb3aec976-68c7-495e-bf78-5943e93d5a18.png?alt=media)

If you organize your endpoint in a folder named group1, the endpoint can be invoked using the following URL: https\:////group\_1/function\_1 .

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ae16da1bcf4fa664da3019f86623409d2640b094%2Fcb1f1a6f-f50c-44dc-93c8-b2b55c3c6ffa.png?alt=media)

The endpoint logicnet is the place where you start modeling the logic, and you can use all modeling components except for form nodes that post information to the UI.

## Special Endpoints

The system treats differently those endpoints with the following names: *main*, *get*, *post*, *put*, *delete*, and *patch*. If your endpoint is named one of those you do not need to include that name in your URL. For example, the URL to invoke the *main* logicnet would be https\:///\<start code of your web service .

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-15066e5e7faa3f9b3df984cbb975e1335cff2b60%2F7cc3c4c3-5780-4e43-92ea-b66292bcf91e.png?alt=media)

The name *main* does not need to appear in the URL, as *main* resolves to the parent folder in the endpoints folder. With *main* it is also possible to model one single (main-)entry of your web service application where you could route the call further to other logicnets within your application

The URL to invoke the *post* logicnet would be https\:/// but with the HTTP method POST.

## Special Folder/Endpoint Names

Another special folder/endpoint name is the following format: *\_\_\_\_*

With this format you indicate that the name is a wildcard in the URL, and that it should be parsed and stored in the variable with *\<variable\_name>.*

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-7a6d7a12e386f5bffd6fe5fc84e994fe46d8e6a9%2F9cc07c47-5f27-462d-b367-acd8890b31c0.png?alt=media)

The URL to invoke the *get* logicnet in the *resource\_1\\\_\_id\_\_* folder would be as follows:

> https\:////resource\_1/ **12SDAFDFS**
>
> Notice that 12SDAFDFS will be matched upon \_\_id\_\_ and consequently stored in the parameter: ‘id’

This is especially helpful if you want to implement a REST API and access resources by their ID in the URL.


---

# 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://community-test.logicnets.com/release-9/design-considerations-and-frameworks/frameworks/web-services-framework/web-services-endpoints.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.