When using the Product Configurator API (/connect/cpq/configurator/actions/configure), a transactionContextId is returned in the response. This context ID is reused in subsequent API calls to add, update, or delete products within the same configuration session. If the context ID expires, subsequent API calls will fail. This article explains the TTL behavior and configuration options.
The transactionContextId has a configurable Time to Live (TTL) that determines how long it remains valid.
Default and Maximum Values:
Where to Configure:
Navigate to the Context Definition and update the TTL value as needed (up to the supported maximum of 45 minutes).
Important Behavior:
The TTL is measured from creation time, not from last access. If TTL is set to 20 minutes, the context expires exactly 20 minutes after creation regardless of activity.
Once expired, a new configuration session must be initiated to get a fresh context ID.
Setting a longer TTL means the context may not reflect the latest changes made to records in the database by other users or applications during that window.
005388357

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.