> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/administration/solutions/soap-functions.md).

# SOAP Functions

{% hint style="info" %}
SOAP functions are only visible in the list if the Solution Creator defined functions that use the [SOAP data provider](/building-apps-with-jigx/data/data-providers.md). Make sure that credentials such as API Keys are set up correctly in [Credentials](/administration/solutions/credentials.md) if they are being referenced in the function definition.
{% endhint %}

You can try out all functions of the solutions that use the SOAP data provider.

1. On the left side, you will see all input parameters of the function including the initial set values.
2. Enter values into the input parameter fields and click the **Preview** button at the top of the screen. The JSON editor on the right side will show the result returned by the function.
3. Click on **Show schema** to view the function definition.

{% hint style="success" %}
You can click the **copy to the clipboard** icon at the top and paste the JSON result into [JSONata Exerciser](https://try.jsonata.org/). This allows you to run and test [Expressions](/building-apps-with-jigx/logic/expressions.md) against real SOAP response data.
{% endhint %}


---

# 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.jigx.com/administration/solutions/soap-functions.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.