Footer Section
Explore
Adobe Sign ServicesAdvantage Platform AdministrationApprovals for Advantage PlatformApprovals for SalesforceBilling for Advantage PlatformBilling for SalesforceCLM for Advantage PlatformCLM for SalesforceContracts for SalesforceCollaborateComposer for Advantage PlatformComposer for SalesforceContractsConga for Google DocsConga Upgrade ProgramContract Intelligence (Standalone)Conga CopilotCPQ for Advantage PlatformCPQ for SalesforceDeal MaximizerDigital Commerce for Advantage PlatformDigital Commerce for SalesforceDiscovery AI for Advantage PlatformDiscovery AI for SalesforceDocusign ServiceseSignature Integration with Advantage PlatformGridInvoice GenerationMix FormsOrchestrateOrder Management for Advantage PlatformOrder Management for SalesforcePartner Commerce for Advantage PlatformPartner Commerce for SalesforceQuote GenerationSign for Advantage PlatformSign for SalesforceSmart SearchTest AuthorTurboEnginesX-Author for Contracts 1.0 (Classic)X-Author for ContractsX-Author for Contracts Advanced for Advantage PlatformX-Author for Contracts Advanced for SalesforceX-Author for ExcelX-Author for Migration Manager for Advantage PlatformX-Author for Migration ManagerRelease NotesGeneral
Add Option to Bundle
post
/carts/{cartId}/items/{cartItemId}/options
The options post endpoint can be used to add options to an existing cart item.
cartId
stringThe reference id of the cart. It can be set to 'active' to use the current active cart for the user.
Example:
a1I3I000000e7GLUAY
cartItemId
stringThe reference of the cart item representing the parent bundle product.
Example:
a133I000000ThrKQAS
alias
booleanThe namespace for the fields is prefixed if set to False. By default it is True.
Example:
false
price
stringThe pricing strategy to use. 'default' | 'async' | 'skip'
Example:
skip
rule
stringThe rule strategy to use. 'default' | 'async' | 'skip'
Example:
skip
x-account
stringThe account value from the header is taken as default account if passed as query parameter.
Example:
0011900000hnGsr
Content-Type
stringContent type of the request body.
Example:
application/json
x-storefront
stringThe name of the storefront used for the request.
Example:
ECommerce
Request body can be a single record or an array of records if multiple options are to be added. The body of the request should contain an object containing the primitive string id of the option you want added to the bundle along with the quantity to be added.
ProductId
stringQuantity
numberSellingTerm
numberProductAttributes
objectLineItem
objectResponses
200
OK
responses
/
200
Rules
array[object]ActionProductIds
stringTriggeringProductIds
stringSuggestedProductIds
stringIsTargetOption
booleanpending
booleanConstraintRuleActionId
stringConfigurationId
stringMessage
stringId
stringName
stringLineItems
array[object]Product
objectAttributeValue
objectLineSequence
integerLineType
stringLineStatus
stringLineNumber
integerItemSequence
integerQuantity
integerProductId
stringPrimaryLineNumber
integerName
stringIsPrimaryLine
booleanId
stringUsername
:Password
:::::::::
curl --request POST \--url https://documentation.conga.com/carts/cartId/items/cartItemId/options \--header 'Accept: application/json' \--header 'Authorization: Basic 123' \--header 'Content-Type: application/json' \--header 'x-account: ' \--header 'x-storefront: ' \--data '{"ProductId": "01t4R00000J5R6i","Quantity": 1,"SellingTerm": 1,"ProductAttributes": {"AutoABOPicklist__c": "Option3"},"LineItem": []}'
Large examples are not rendered by default.
chevron_right