> 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/advanced-topics/system-integration/web-services-integration.md).

# Web Services Integration

Web services are the preferred way of integrating LogicNets applications with external systems.

* LogicNets applications can call to web services of external systems to retrieve data, send updates, and perform operations.
* LogicNets applications can be built as web services, exposing application functionality to external systems.

## Protocols, Representations, and Authorization

LogicNets supports the following:

* Supported transfer protocols: HTTP/HTTPS, certificates (only with HTTPS)
* Supported representations: XML, JSON, FHIR (in JSON format)
* Authorization: basic authentication, OAuth bearer token, certificates

## LogicNets Parts

* LogicNets has a [*CallWebservice*](/release-9/platform-documentation/process-node-parts/call-a-generic-webservice.md) part available to call web services.
* LogicNets has a [*Web Services*](/release-9/design-considerations-and-frameworks/frameworks/web-services-framework.md) framework available for implementation of your own web services (SOAP, REST).

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-abe80027ff870f6f9c52ce48d9366bac5157fd2c%2Fa190a81a-a9d2-427b-9e64-f6557336a2f9.png?alt=media)


---

# 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/advanced-topics/system-integration/web-services-integration.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.