Hello,

My understanding around this from a previous inquiry, is that there are no APIs to pull data from Sage 500.  There are only APIs/Data Migration routines to import data to it.  The documentation for these are part of the Sage 500 SDK. 

If all you need to do is pull data from Sage 500, you'll need to become familiar with the schema browser that comes with Sage 500 and how all the tables are structured and relate.  I would also suggest looking at the views that populate the various Business Insight Explorers as they may have much of the data you are looking for already formatted for you.  These SQL views are prefixed with vdv (Example: vdvCustomer).

Hello,

My understanding around this from a previous inquiry, is that there are no APIs to pull data from Sage 500.  There are only APIs/Data Migration routines to import data to it.  The documentation for these are part of the Sage 500 SDK. 

If all you need to do is pull data from Sage 500, you'll need to become familiar with the schema browser that comes with Sage 500 and how all the tables are structured and relate.  I would also suggest looking at the views that populate the various Business Insight Explorers as they may have much of the data you are looking for already formatted for you.  These SQL views are prefixed with vdv (Example: vdvCustomer).

Rafael said:

The documentation for these are part of the Sage 500 SDK. 

Do I need to purchase Sage 500 SDK to be able to view the aPI documentation?

Here's a link to the SDK from our knowledgeable. 

support.na.sage.com/.../viewContent.do

is this free or need to subscribe?

You would get better help if you gave specifics on what you were looking to do.

I need the API documentation for Sage 500

I do not believe there is formal API documentation available, which is probably why John suggested that what you were looking to do was better.  Sage 500 has several stored procedures used to move data around, many of which have the term "API" in their name.  When someone wants to do something specifically, people can often then recommend which stored procedures to take a look at.

RKL has documentation on several APIs -- both those that were originally developed by Sage's Professional Services Group as well as custom APIs developed by RKL. Separate documentation was written specifically for each import task, and that is likely why @JohnHanrahan was suggesting we can be more helpful if you gave specifics on what you were looking to do.