> 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/general-technical/webservice-integration-technical-documentation-examples.md).

# Webservice Integration Technical Documentation & Examples

Unimarket utilizes two primary messaging standards for integration: **uXML (Unimarket XML)** for proprietary platform functions and **cXML (Commerce XML)** for industry-standard procurement transactions.

## uXML Integration Points

uXML is used for specialized platform functions that fall outside the standard cXML scope. These are typically used to synchronize master data or handle real-time validation between Unimarket and your ERP.

### Key uXML Message Types

* **Account Code Validation**: Real-time synchronous check for budget and GL validity at checkout.
* **Approval Configuration**: Inbound sync of approval chains, levels, and groups.
* **User Details**: Synchronization of user roles and organization units from a master identity source.
* **General Ledger (GL) Transactions**: Sending accounting strings for commitments (orders) and accruals (receipts).

uXML requests are typically sent over [POX](/documentation/general-technical/sending-pox-messages-to-unimarket.md) or [SOAP](/documentation/general-technical/sending-soap-messages-to-unimarket.md) transports.

## cXML Integration Points

Unimarket adheres to the global **cXML standard** (v1.2.021+) for high-volume transactional data. This ensures compatibility with thousands of suppliers and major ERP systems like Workday, Oracle, and SAP.

### Common cXML Integrations

* **Punchout (Roundtrip)**: Allows users to "punch out" from their ERP into Unimarket or from Unimarket into a supplier's website.
* **OrderRequest**: The standard message used to transmit Purchase Order details to suppliers or external finance systems. See [Purchase Order (OrderRequest) Technical Documentation](/documentation/transactions-orders-receipts-invoices-and-more/order-request-technical-documentation.md).
* **InvoiceDetailRequest**: Inbound electronic invoices (eInvoicing) sent from suppliers to Unimarket for matching and payment.
* **ShipNoticeRequest**: Outbound notification from suppliers regarding shipment status.

## Integration Documentation Resources

For technical teams and developers, the following resources are essential for mapping and testing:

| Resource Type                | Description                                                                                                                                                                                                                                                                                   |
| ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Webservice Documentation** | Comprehensive guides for configuring endpoints and security. [View the documentation](http://admin.unimarket.com/unimarket-integration-docu/1.1/index.html) or [download the complete documentation and examples](https://admin.unimarket.com/unimarket-integration-docu_1.1.zip) (zip file). |
| **XML Schema (XSD)**         | Formal definitions for validating uXML messages.                                                                                                                                                                                                                                              |

## Which Standard Should You Use?

* Use **cXML** if you are setting up standard **Order or Invoice** automation with a major supplier or ERP.
* Use **uXML** for **Platform Administration**, such as synchronizing your budget data, approval hierarchies, or user role assignments.

{% hint style="info" %}
For details on transporting uXML requests, see [Sending POX (Plain Old XML) Messages to Unimarket](/documentation/general-technical/sending-pox-messages-to-unimarket.md) and [Sending SOAP Messages to Unimarket](/documentation/general-technical/sending-soap-messages-to-unimarket.md).
{% 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 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/general-technical/webservice-integration-technical-documentation-examples.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.