> For the complete documentation index, see [llms.txt](https://developer.ultimo.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ultimo.net/api-guide/third-party-integration.md).

# Third party integration

:no\_entry\_sign:Professional :white\_check\_mark:Premium :white\_check\_mark:Enterprise

## Connecting to third party web services

Ultimo Business Integration is able to connect with third party web services. Both import and export connectors offer the possibility to send requests to a webservice url. By default, the request will be sent in a fixed Ultimo format. It is however possible to send data in a specified custom (xml or json) file format. This can be configured by our consultants.

Ultimo Business Integration is also able to connect with web services that require a Expect: 100-continue header in the initial request.

### Authentication options

The following authentication types are supported when connecting to third party web services:

* Basic authentication
  * Ultimo only supports pre-emptive authentication; the Authorization header is directly send with the first request
* [OAuth2.0](https://oauth.net/2/)
  * Ultimo offers support for grant types Authorization code, Password and Client credentials


---

# 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://developer.ultimo.net/api-guide/third-party-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.