SOAP APIs....

[Jacob]

All SOAP calls into Sugar use soap.php as their entry point. There are several SOAP APIs at this point. The original API implementation is actually in soap.php. This API has been deprecated. All new development should use the APIs located in the soap subfolder.


SoapSugarUsers.php -- Should be used for single user connections. This is the primary API and is able to control all bean types. The Sugar Plug-in for Microsoft Outlook uses this API.

SoapPortalUsers.php -- Should be used for portal applications. Sugar Portal uses this API.
SoapSync.php -- Should be used for bulk data transfer and getting lists of recent changes.


SoapSugarUsers.php has been updated to have JavaDoc comments in the code. This should help developers leverage the API and speed the development process.

There are also a whole bunch of soap test files in the examples folder. Look under examples for all files that start with soap.

Jacob

[skaag]

Hi,

is this post relevant for Sugar v5.1? None of the official (outdated!) docs for SOAP access with Sugar mention different access points for SOAP access.
I am using the nusoap client library included with sugar and all my calls go to SUGAR_ROOT/soap.php?wsdl
Should I change it?

TIA!

[eggsurplus]

You still call soap.php. The files he references are the files that implement the different functions. For example, you'll notice some functions that start with "portal_". You can find those type of functions in SoapPortalUsers.php to look at. You'd still call soap.php to access those functions though.

Does that help?