The Sage 300 ERP Web SDK is available on the official GitHub repository: SageNADev/Sage300-SDK.

API leverages Swagger, which is a very useful tool for handling POST and GET requests to web endpoints, allowing you to pass information into a database.

That said, it’s important to confirm whether the Sage 300 Swagger Web API provides all the functionality you need. Some parts of the API may be incomplete or not released yet, so reviewing the Swagger interface for the web screens is essential.

In addition to the Web API, Sage 300 also includes COMAPI.dll, which is installed in the runtime folder and ready for use. Unlike the official SDK which requires a paid license. If your team is concerned about documentation or planning a more complex integration, it may be worthwhile looking into the SDK.

But back on track!

The COMAPI.dll is a powerful tool, though it does have some limitations. For example, it requires a Sage 300 login, which consumes a license on use. However, you can control how the login is managed with code and how you interact with the endpoint if you so choice to build one. A practical way to get started is by recording a macro in Sage 300. Be sure to capture all field changes during recording—this will expose the field names and required data that is going to be used, saving you time! This will generate some code, which you can then convert into .NET or C# for broader use. You may even find some good examples online in C#. 

Finally, keep in mind that COMAPI is not the same as the Web API or the SDK. If your project requires a web endpoint, you’ll need to build and publish one yourself using COMAPI.I hope it helps point you in the right direction and good luck!

The Sage 300 ERP Web SDK is available on the official GitHub repository: SageNADev/Sage300-SDK.

API leverages Swagger, which is a very useful tool for handling POST and GET requests to web endpoints, allowing you to pass information into a database.

That said, it’s important to confirm whether the Sage 300 Swagger Web API provides all the functionality you need. Some parts of the API may be incomplete or not released yet, so reviewing the Swagger interface for the web screens is essential.

In addition to the Web API, Sage 300 also includes COMAPI.dll, which is installed in the runtime folder and ready for use. Unlike the official SDK which requires a paid license. If your team is concerned about documentation or planning a more complex integration, it may be worthwhile looking into the SDK.

But back on track!

The COMAPI.dll is a powerful tool, though it does have some limitations. For example, it requires a Sage 300 login, which consumes a license on use. However, you can control how the login is managed with code and how you interact with the endpoint if you so choice to build one. A practical way to get started is by recording a macro in Sage 300. Be sure to capture all field changes during recording—this will expose the field names and required data that is going to be used, saving you time! This will generate some code, which you can then convert into .NET or C# for broader use. You may even find some good examples online in C#. 

Finally, keep in mind that COMAPI is not the same as the Web API or the SDK. If your project requires a web endpoint, you’ll need to build and publish one yourself using COMAPI.I hope it helps point you in the right direction and good luck!