Revenue Cloud Developer Guide
j
No Results
Search Tips:
- Please consider misspellings
- Try different search keywords
QOC Qualification
Input representation of the qualification request.
- JSON example
-
{ "productIds": [ "01txx0000006i7PAAQ", "01txx0000006i7QAAQ", "01txx0000006i7IAAQ" ], "userContext": { "accountId": "001xx000003GZHgAAO" } } - Properties
-
Name Type Description Required or Optional Available Version additionalContextData Context Data Input[] Additional nodes that are added to the custom or default context definition. The maximum number of supported nodes is 10. Optional 60.0 catalogId String ID of the catalog. Optional 60.0 categoryId String ID of the category. Optional 60.0 contextDefinition String API name of the custom context definition that’s sent for context creation. If this property isn’t specified, the default context definition is used. Optional 60.0 contextMapping String Default context mapping of the context definition. If a context mapping is specified, then the API checks whether the mapping belongs to the specified context definition to process the details for hydration. Optional 60.0 correlationId String Unique identifier of the request. Optional 60.0 productIds String[] List of product IDs for qualification check. Required 60.0 qualificationProcedure String API name of the custom qualification procedure that’s sent for processing. If this property isn’t specified, the default qualification procedure is executed. Optional 60.0 userContext User Context Input User context details. For example, account ID or contact ID. Optional 60.0