> For the complete documentation index, see [llms.txt](https://docs.unimarket.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unimarket.com/documentation/unimarket-integration-middleware/unimarket-connector-platform.md).

# Unimarket Connector Platform

The buying organization can choose to integrate via standard Unimarket web services or use the Unimarket Connector middleware to manage data transformation with external systems like FMIS, ERP, or reporting systems.

## Transition to Workato On-Premise Agent (OPA)

{% hint style="info" %}
Unimarket has transitioned to using the [Workato On-Premise Agent (OPA)](/documentation/unimarket-integration-middleware/workato-on-premise-agent-opa.md) for all new customer integrations. The Unimarket Connector Platform (UCP) is no longer being installed for new customers, and existing customers are being upgraded to Workato for improved security and performance. Support for the legacy UCP is expected to continue through the end of 2026.
{% endhint %}

## The Unimarket Connector (Legacy)

The Connector was designed to minimize custom integration requirements by specifically handling the transmission, receipt, and transformation of messages between Unimarket and client-side systems.

* **Installation**: Installed on a Java Runtime Environment (JRE) behind the customer firewall.
* **Function**: Receives XML messages from the Unimarket application.
* **Output**: Converts data into a compatible format (such as a flat file) for the customer's FMIS/ERP system.
* **Delivery**: Data is typically sent to a staging table or a specific directory location.

## Types of Integration Messages

Integration points facilitate the exchange of several data types between systems:

| Category               | Examples                                                        |
| ---------------------- | --------------------------------------------------------------- |
| Transactional Messages | Orders, Receipts, and Invoices.                                 |
| Master Data            | Approvals, User Details, and Accounting (GL) information.       |
| Validation / Callback  | Budget Checking, Approvals, and User Validation/Authentication. |

{% hint style="info" %}
The diagram below does not illustrate all the available integration points.
{% endhint %}

![Unimarket Connector integration points](https://help.unimarket.com/hc/article_attachments/53674577887641)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.unimarket.com/documentation/unimarket-integration-middleware/unimarket-connector-platform.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.