> For the complete documentation index, see [llms.txt](https://docs.greytrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.greytrix.com/gumu-salesforce-integration/sage100/greytrix-sage100-webapi-installation.md).

# Greytrix Sage100 WEBAPI Installation

Sage has announced that **SData will be deprecated in Sage 100 ERP starting with the 2025 release (April 2025)**, requiring customers to transition to alternative integration methods to maintain system connectivity.

To address this, Greytrix has introduced the **Sage 100 Web API**, a secure and modern replacement for SData. It enables seamless integration with external systems, supports two-way data exchange, and provides a comprehensive set of standard and customizable endpoints. The solution is designed for easy implementation and testing using tools like Swagger and Postman, while ensuring that **all existing SData functionalities remain fully supported**, allowing for a smooth and efficient transition.


---

# 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.greytrix.com/gumu-salesforce-integration/sage100/greytrix-sage100-webapi-installation.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.