> 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/master-data/approval-request-response-integration.md).

# Approval Request/Response Integration

The **Approval Request / Response** messages facilitate a two-way, real-time integration. That allows Unimarket to retrieve approver information directly from an external ERP or Finance system, as a requisition progresses.

## How it Works

When a requisition is created and routed for approval, Unimarket triggers an integration request to the external system to identify the next required approver. This process repeats at each step of the workflow, until all necessary approvals are secured.

## Use Cases

This integration is an ideal alternative to the standard **Approval Configuration Request** (loading master data) in the following scenarios:

* **Dynamic Rules**: The organization has highly complex approval logic in their ERP that would be difficult or inefficient to replicate within Unimarket.
* **Single Source of Truth**: The customer prefers to keep all approval data and hierarchy maintenance exclusively, within their external Finance system.
* **Reduced Maintenance**: It removes the need to perform regular bulk uploads of approval groups, chains, and rulesets into Unimarket. See [Approval Data Uploads via SFTP](/documentation/file-automation-sftp/approval-data-uploads-via-sftp.md) for details on the file-based alternative.

## Comparison of Approval Methods

| Feature           | Master Data Upload (File Automation) | Approval Request Integration               |
| ----------------- | ------------------------------------ | ------------------------------------------ |
| **Data Location** | Loaded into Unimarket                | Stays in ERP/Finance system                |
| **Processing**    | Rules evaluated by Unimarket         | Rules evaluated by external system         |
| **Speed**         | Instant evaluation within the app    | Dependent on external system response time |
| **Complexity**    | Best for standard hierarchies        | Best for complex, dynamic logic            |

## Technical Requirements

* **Communication**: This is an active, real-time integration point requiring a stable connection via the **Workato On-Premise Agent** or **Unimarket Connector**.
* **Response**: The external system must respond with a valid approver identity, that exists within the Unimarket community.


---

# 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/master-data/approval-request-response-integration.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.