# 2.2 Customization

In its non modified form, our solution is designed to work with a specific API from one Enterprise System ([weclapp](https://www.weclapp.com/en/) - [purchase orders](https://www.weclapp.com/api/#!/purchaseOrder/get_purchaseOrder)). But due to our architecture, we are able to leverage other APIs as well. 

To setup the  project for a different system / data / API, users need to change the projects code. There are three code segments where changes need to be done:

* API / rest defintion and 
* Data pre-processing 
* Custom Transformer in the data pipeline

:construction: *We are working to provide better defined code segments where custom code has to be imported. unfortunately at this point the project is focused on customer specific development and these solutions are not finished jet.*


---

# Agent Instructions: 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:

```
GET https://jmu-isgroup.gitbook.io/anomalydetection.ml/installation-and-use/2.-installation-and-usage/2.2-customization.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.