---
schema_version: "1"
id: 842f82d644e2c3834a6af556c4a1fed5b6c3e211a91f519d30ca00865bb77c80
title: Post Offer Details with Configuration API
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/industries/cme/guides/comms-t-post-offer-details-with-configuration-api.md
canonical_url: https://developer.salesforce.com/docs/industries/cme/guide/comms-t-post-offer-details-with-configuration-api.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: a10c2da7b76c2a7dd190e31c991e715b7371b3a199d6f1b6bbbf9b86afafcf62
products:
  - Communications, Media, Energy and Utilities APIs (Managed Package)
  - Industries Developer Documentation
---
# Post Offer Details with Configuration API

This API provides the ability to configure an offer (either a product or promotion) and view updated prices, quantities, and attributes. The API returns the configured product details.

The configured product details are cached so that subsequent requests for the same configuration are retrieved with the data in the current cache layer.

Validations, prices, adjustments, overrides, rules, context, and so on are resolved internally. The Salesforce ID is not used as part of the request or response parameters. If validation fails, the OfferDetails structure is returned with an appropriate error message.

The CME Fall '20 release includes an Attribute Basket Cache feature. See [Attribute Basket Cache Exclusion](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-attribute-basket-cache-exclusion.md).

Starting in CME Spring '22, Digital Commerce supports Usage Based Pricing. You can define usage-based price charges for each Product. If the usage-based price is not available, you can set it up using Attribute-Based Pricing. You can update usage quantity by either:

- Updating the UsageQuantity Field.

- Using Attribute Binding, which takes precedence over the field update if both values are passed.

For more information, see [Create Attribute Bindings for Usage Pricing](https://help.salesforce.com/s/articleView?id=ind.comms_create_attribute_bindings_for_usage_pricing.htm).

## Rules Supported

- [Context Eligibility Rules](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-context-eligibility-rules.md) for known users are supported.

- Pricing Interface (see [Attribute-Based Pricing](https://help.salesforce.com/s/articleView?id=ind.comms_attribute_based_pricing.htm))

- Product Validation Interface (see [Context Rules Framework](https://help.salesforce.com/s/articleView?id=ind.comms_context_rules_framework.htm) and [Advanced Rules Framework](https://help.salesforce.com/s/articleView?id=ind.comms_advanced_rules_framework.htm))

- For anonymous users, [Advanced Rules](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-advanced-rules.md) are supported for [Defining Advanced Rules Using Configuration Type](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-defining-advanced-rules-using-configuration-type.md) and [Defining Advanced Rules Using Attribute Configuration Type](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-defining-advanced-rules-using-attribute-configuration-type.md) only.

- For known users, [Advanced Rules](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-advanced-rules.md) are supported for [Defining Advanced Rules Using Configuration Type](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-defining-advanced-rules-using-configuration-type.md) and [Defining Advanced Rules Using Attribute Configuration Type](https://developer.salesforce.com/docs/industries/cme/guide/comms-t-defining-advanced-rules-using-attribute-configuration-type.md) only.

- [Product Relationships](https://help.salesforce.com/s/articleView?id=ind.comms_product_relationships_overview.htm) are supported with filters, for example, product A removes Product B.

- [Pricing](https://help.salesforce.com/s/articleView?id=ind.comms_pricing_definition.htm) is supported. However, for pricing, do not use Pricing for Advance Rules. Always use the Custom Pricing Plan, which triggers [Attribute-Based Pricing](https://help.salesforce.com/s/articleView?id=ind.comms_attribute_based_pricing.htm).

- Also, see [Using Context Rules with Digital Commerce APIs](https://help.salesforce.com/s/articleView?id=ind.comms_using_context_rules_with_digital_commerce_apis.htm)

## Prerequisites

- The catalog should have CatalogCode**c populated. Spaces are not allowed in CatalogCode**c.

- Products should have ProductCode populated. Spaces are not allowed in ProductCode.

- Promotions should have Code**c populated. Spaces are not allowed in Code**c.

- The catalog should be present with products and promotions attached to it as records under the CatalogProductRelationship\_\_c object.

- The catalog should be attached to a default price list through DefaultPriceList**c field on Catalog**c object.

- Price list entries should exist for all products attached to the catalog.

- Create a custom setting called [CacheAPIFields](https://help.salesforce.com/s/articleView?id=ind.comms_t_cpq_configuration_settings_reference_148927.htm) with a value of true. CacheAPIFields is not required for CME 103.1.14 and later versions.

## Parameters

For API parameter names and descriptions, see [Digital Commerce REST API](https://developer.salesforce.com/docs/industries/cme/references/dc-rest1?meta=Summary)

## Response

For detailed API response descriptions, see [Digital Commerce REST API](https://developer.salesforce.com/docs/industries/cme/references/dc-rest1?meta=Summary).