CPQ Cloud exposes asset data through REST APIs. Asset REST APIs support create, read, update, delete, and synchronize. They also provide import and export operations, and operations for external orders.

These operations provide the ability to maintain CPQ assets through RESTful services. These endpoints provide access to actions to open, create, update, delete, and synchronize assets.

These operations allow external systems to modify, terminate, suspend, resume, renew, reconfigure, and create follow-on orders for assets.

Theses opertations provide the ability to export, import, and retrieve assets and asset log files.

The Calculate Price REST API allows an external application to query CPQ Cloud for pricing information. CPQ Cloud executes contract rules and relevant profiles to calculate and return the final list price.

CPQ Cloud exposes transactional objects and transaction data through REST APIs and RESTful standards. The REST APIs provide a new, modern way to access transaction and line item information. With appropriate HTTP Basic authentication, any other third-party system can make use of these services. Additional resources allow credentialed third-party systems to create transactions, and to update transactions by invoking modify, version, submit and approval actions in a Commerce Process through REST APIs.

Transaction Administration services return CPQ transaction desktop layout definitions for UI frameworks to consume. The desktop layout definitions contain: layout parameters and properties for panels, tabs, columns, action strips, and transaction line grids; properties for actions and attributes; and translations for layout items. Metadata Services expose information about the definitions of the Commerce main document, sub document, actions, attributes, and translations.

These services return the action metadata for the specified Commerce main document or sub document. The action metadata is comprised of: defined action properties that are defined on the Admin Action page; possible action states (i.e. visible or enabled); dependencies and possible states (if an action can be altered by a step or rule); and links to the current REST call, parent items, and translations.

These services return the array set metadata for the specified Commerce document. The array set metadata is comprised of: defined attribute properties that are defined on the Attribute Editor page; possible attribute states, (updatable, required, visible, domain, messages, hasError, hasWarning, or hasContraintViolation); dependencies and possible states, if an attribute can be altered by a formula, step, or rule; and links to the current REST call, parent items, menu items, and translations.

These services return the attribute metadata for the specified Commerce document. The attribute metadata is comprised of: defined attribute properties that are defined on the Attribute Editor page; possible attribute states, (updatable, required, visible, domain, messages, hasError, hasWarning, or hasContraintViolation); dependencies and possible states, if an attribute can be altered by a formula, step, or rule; and links to the current REST call, parent items, menu items, and translations.

These services return the menu item metadata for the specified attribute. The menu are returned as composite values containing menu properties and domain items. Links to the current REST call, parent items, and translations are also returned.

The translation services retrieve translations for actions, attributes, and menu items. Translations for all site-supported languages can be retrieved. If a translation is not defined, an empty string is returned for the requested value. The following fields are translatable: Actions (labels and descriptions), Attributes (labels, descriptions, and user defaults), and Menu Items (display values). When translations are requested, translations that have an empty value for all the properties are not returned. Translation data is returned if any of the property values are populated.

Commerce Actions provide the ability to maintain CPQ Transaction documents through RESTful services. These endpoints provide access to actions to open, create, copy, delete, reconfigure, save, email, and print Transactions. They also provide services for currency management and cache interaction.

Commerce Document Generation Actions provide services to generate proposals, and document compare and merge features for Contract Negotiation.

Commerce Order Actions provide REST services for order fulfillment actions.

Commerce Submit Actions provide access to Submit actions to request approval, reject, revise, and approve submitted Transactions.

Commerce Sub Document Actions provide the ability to maintain CPQ Transaction Line items through RESTful services. These endpoints provide access to actions to open, create, copy, delete, reconfigure, update, save, email and print Transaction Line items. They also provide services for navigation and cache interaction.

The Configuration Run-Time Data endpoints expose information and perform an action for a model. All Configuration Run-Time Data REST APIs follow a required product hierarchy starting with the product family then product line followed by the model. A variable name for the product entity is required. For example, /config{prodFamVarName}.(prodLineVarName}.{modelVarName}/ is the standard Configuration Run-Time Data product path for an endpoint URL.

The custom{DataTable} REST API allows an external system to access deployed data in CPQ Cloud Data Tables. When executed correctly, the external system will receive the CPQ Cloud Data Table's deployed data in the REST response body. NOTE: Currently only Read operations are supported when interacting with the custom{DataTable} API.

CPQ Cloud exposes eligibility data through REST APIs. As described in this section, Eligibility APIs allow external applications to create, read, update, delete, and deploy eligibility data.

These operations retrive conditions and selections for Eligibility Rules.

This REST API provides support for the External Configurator Integration. The REST service invokes the External Configurator Advanced Save function to create a transaction, Add from Catalog, or Reconfigure.

The Document Generator REST APIs allow an external system to send a REST call to generate a document using a Document Designer template and retrieve generated documents.

The REST APIs enable an external entity to use an existing Email Designer template and generate an html email for a given transaction. The API allows POST with the Transaction ID and appropriate Email Designer template details, to create the output email.

The REST API enables retrieving data about a sales user's activities and observed performance or other metrics during their interaction with the application. The information also provides application time as well as category information which can be used by customers to build their benchmark monitoring systems and proactively tackle any performance issues.

Theses opertations provide the ability to export Performance Log events.

These actions retrieve the list of price books or the specified price book.

The Search Parts REST API supports customizing the REST response by specifying an advanced query object (i.e. 'q' criteria) as a request body parameter. This allows administrators to customize the query by specifying various combinations of criteria.

CPQ Cloud customers can leverage identity management solutions such as Oracle Identity Cloud Service (IDCS) to simplify the administration of users and passwords. CPQ Cloud's integration features simplify the implementation of identity services for Enterprise customers by allowing customers to delegate user management activities such as user creation, activation, revocation, and password management for host company users to IDCS or other Identity Service providers.