SOAP Users API with Web Services 2.0
Overview
You can generate a skeleton input for each operation in the Users WSDL, which contains the following operations:
- addUsers
- updateUsers
- getUser
- resetPassword
For each operation, the following fields are always required in the header:
-
UsernameToken
- Username
- Password Type
- category: Security
- schemaLocation
Users SOAP API Details
For all SOAP APIs, the Failure Response Variables are exceptionCode
and exceptionMessage
.
SOAP API | Description | Required Input Variables | Success Response Variables |
---|---|---|---|
addUsers | Adds a user through SOAP. When multiple users are created using this method, the entire request is processed before a response is sent. |
Note: These fields are the minimum requirement to add a user. The following fields will be set with default values if the values are not set in the Web Services Users API.
|
|
updateUsers | Updates user information through SOAP. |
|
|
getUser | Grabs user information through SOAP. |
|
|
resetPasswords | Resets user passwords through SOAP. |
|
|
Administration
Accessing the Users WSDL and Generating Skeleton Input
- Click Admin to go to the Admin Home Page.
-
Click Web Services in the Integration Platform section.
The Web Services Test page opens.
- Confirm that the Web Service Version is 2.0.
- Click the Users tab.
- Select an API from the drop-down.
- Enter data for the User Login.
-
Click Generate Input to retrieve the skeleton.
For more information on the body of the Users Web Service, and for code examples, see the topic SOAP Users API with Web Services 1.0. With the exception of the header, the Web Services 1.0 code examples are valid in Web Services 2.0.
Header Information for Web Services 2.0
For each API, the body of the SOAP XML is the same as it was for Web Services 1.0. This is the information contained between the <soapenv:Body> and </soapenv:Body> tags.
Comment | Header: Web Services 1.0 | Header: Web Services 2.0 |
---|---|---|
No change | <soapenv:Header> | <soapenv:Header> |
New tags |
<wsse:Security xmlns:wsse= "http://docs.oasis-open.org/wss/2004/ |
|
New user information replaces sessionId |
<bm:userInfo . . . >
</bm:userInfo> |
<wsse:UsernameToken wsu:Id="UsernameToken-2">
</wsse:UsernameToken> |
This is now in the URL, with the unique end point specified. | <bm:category xmlns:bm="urn:soap.bigmachines.com"> Commerce </bm:category> |
Now reflected in the SOAP Server URL field. |
No longer needed |
<bm:xsdInfo . . . . . </bm:xsdInfo> |
|
Ending the new authentication |
</wsse:Security> |
|
No change | </soapenv:Header> | </soapenv:Header> |