> 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/platform-documentation/process-node-parts/call-internal-webservice.md).

# Call Internal Webservice

## Description

This part allows users to enable their logicnet-based application to perform a web service call to a webservice that is hosted on the same installation. Please use the *call webservice* part if a webservice is hosted elsewhere.

## Use

The call internal webservice part is available from the "web services" option in a process node. When you select the part, enter the connection information for the webservice to which to connect. The system can store the response in the application context.

## Editor Fields

| Field                           | Description/Use                                                                                                                               | Type/Options | Optional/Mandatory |
| ------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Result code path                | This is the path of the data object in which the result code will be saved.                                                                   | Data Object  | Mandatory          |
| Response path                   | This is the path of the data object in which the response will be saved.                                                                      | Data Object  | Mandatory          |
| Trace full request and response | Check this box to have the full request and response data output to debug tracing (only traced if debug tracing is enabled).                  | Checkbox     | Optional           |
| Method                          | This is the call method associated with the particular web service.                                                                           | GET \| POST  | Mandatory          |
| Path                            | This is the path of the web service call.                                                                                                     | Text         | Optional           |
| Content type                    | This is the content type for the web service call.                                                                                            | Text         | Optional           |
| Soap action                     | This is the SOAP soap action of the web service call.                                                                                         | Text         | Optional           |
| Maximum redirects               | This is the maximum number of redirects the system should allow for the web service call.                                                     | Number       | Optional           |
| Custom headers                  | This is where the user enters any customized headers the system should add to the web service call.                                           | Collection   | Optional           |
| Request                         | This field is only required when the method is set to "POST". It is the request that the system should send.                                  | Text         | Optional           |
| Asynchronously                  | <p><strong>Yes</strong>: Call the webservice asynchronously.<br><strong>No</strong>: Call the webservice synchronously.</p>                   | Yes \| No    | Mandatory          |
| Worker-handle                   | This is only required when "Asynchronously" is set to "Yes". It is the name of the worker handle to handle the asynchronous web service call. | Text         | Optional           |

## Example

To see the Call Internal Webservice part working, download the [example projects](/release-9/example-gallery/example-projects-for-parts/call-internal-webservice-example-project.md) in your workspace.


---

# 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/platform-documentation/process-node-parts/call-internal-webservice.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.