You are here: Integrating With CPQ Cloud > Web Services 1.0 and SOAP APIs > An Overview of SOAP APIs and Web Services 1.0

An Overview of SOAP APIs and Web Services 1.0

OVERVIEW

The system allows the FullAccess user to setup all their products, configuration, and Commerce Processes details. The FullAccess user is able to define and change details of their products, rules to be applied on configuring a product and finally create and update their Commerce Processes, which form the basis of a particular commerce transaction. An application wanting to consume services can use SOAP messages to interact with CPQ Cloud and take advantage of its features.

The CPQ Cloud system supports SOAP API for the purpose of uploading large amounts of system data. System data can be sent through a client program to the CPQ Cloud system.

For sending information to CPQ Cloud system:

  1. Data is sent from a client program to a CPQ Cloud API server and modifies data on your system.
  2. The client program should get the result of the API call with a status field, including pass or fail.

Using a SOAP API, you can perform many useful tasks, such as updating parts and commerce information. You don't have to use FTP clients or the CPQ Cloud interface to upload and download data.

ADMINISTRATION

ClosedWhich version of Web Services do I have?

CPQ Cloud uses Web Services versions 1.0 and 2.0. Different features are available depending on which version of Web Services you are using.

To discover which version of Web Services you are using:

  1. Click Admin to go to the Admin Home Page.
  2. Click Web Services under Integration Platform.

    The Web Services version number is shown under Web Service Version, on the upper left-hand corner of the page.

    ,

    If you have a new installation of CPQ Cloud, or have upgraded to 2014 R2, version 2.0 will be listed.

Even if your installation has been using Web Services 1.0, you can use the features of Web Services 2.0 concurrently.


ClosedSession ID Authentication

CPQ Cloud offers sophisticated category identification and session id authentication for all SOAP APIs. The SOAP Header requires a category element to identify the module, including commerce, security, Data Tables, and so on, to which the API call is being made. There is also a session id validation mechanism providing enhanced security to API calls.


ClosedWhich modules support SOAP calls?


NOTES

RELATED TOPICS

Related Topics Link IconSee Also