Get a Pricing Rule Customer Specific Condition
get
/rest/v19/pricingSetup/rules/{ruleVariableName}/customerSpecificConditions/{conditionId}
Use this endpoint to add a customer specific condition for the specified pricing rule.
Request
Path Parameters
Query Parameters
-
fields: string
This parameter filters the resource attributes. Only the specified attributes are returned, which means that if no attributes are specified, all attributes are returned.
Response
Supported Media Types
- application/json
200 Response
Success
Root Schema : PricingCustomerSpecificCondition
Type:
Show Source
object-
active:
boolean()
Title:
ActiveIndicates whether the condition is active. -
createdBy:
Created By
Title:
Created ByRead Only:trueThe details of the user who created the record. -
customerId:
string()
Title:
Customer IDThe unique identifier of the customer.This should match the Account Lookup's Id field. -
customerName:
string()
Title:
Customer NameRead Only:trueThe name of the customer.This should match the value from Account Lookup's lookupCode -
dateAdded:
string(yyyy-MM-dd'T'HH:mm:ss.SSS'Z')
Title:
Date AddedRead Only:trueCreation date of the Pricing Rule. -
dateModified:
string(yyyy-MM-dd'T'HH:mm:ss.SSS'Z')
Title:
Date ModifiedRead Only:trueLast modified date of the Pricing Rule. -
endDate:
string(yyyy-MM-dd'T'HH:mm:ss.SSS'Z')
Title:
End DateThe date after which the condition will become inactive. -
groupAccessEnabled:
boolean()
Title:
Group Access EnabledRead Only:trueIndicates whether the user has access to the groups segment -
id:
integer()
Title:
IdRead Only:trueThe unique identifier of the customer specific condition. -
lastModifiedBy:
Last Modified By
Title:
Last Modified ByRead Only:trueThe details of the user who modified the record. -
links:
array Links
Title:
LinksRead Only:trueThe link relations associated with the resource instance. -
segmentLevelAccessType:
string()
Title:
Segment-level Access TypeRead Only:trueSegment-level Access Type -
startDate:
string(yyyy-MM-dd'T'HH:mm:ss.SSS'Z')
Title:
Start DateThe date after which the condition will become active.
Nested Schema : Created By
Title:
Created ByRead Only:
trueThe details of the user who created the record.
Match All
The details of the user who created the record.
Show Source
Nested Schema : Last Modified By
Title:
Last Modified ByRead Only:
trueThe details of the user who modified the record.
Match All
The details of the user who modified the record.
Show Source
Nested Schema : Links
Type:
arrayTitle:
LinksRead Only:
trueThe link relations associated with the resource instance.
Show Source
Nested Schema : UserDetails
Type:
Show Source
object-
emailId:
string()
Title:
Email IdEmail Id of the user -
firstName:
string()
Title:
First NameFirst Name of the user -
lastName:
string()
Title:
Last NameLast Name of the user
Examples
The following examples show how to retrieve the specified customer-specific condition for a pricing rule in Pricing Engine by submitting a GET request to the REST resource using cURL. For more information about cURL, see Use cURL.
curl - X GET -H "Authorization: Bearer <token>" - H "Content-type: application/json" https://sitename.oracle.com/rest/v19/pricingSetup/rules/bankingRule/customerSpecificConditions/38581345
Response Body Sample
{
"id": 38581345,
"active": true,
"customerId": "1001",
"customerName": "ABC Solutions, Inc.",
"startDate": "2021-06-22T00:00:00Z",
"endDate": "2021-12-31T23:59:59Z",
"dateModified": "2021-06-22T12:03:34Z",
"dateAdded": "2021-06-22T12:03:34Z",
"links": [{
"rel": "self",
"href": "https://sitename.oracle.com/rest/v19/pricingSetup/rules/bankingRule/customerSpecificConditions/38581345"
}, {
"rel": "parent",
"href": "https://sitename.oracle.com/rest/v19/pricingSetup/rules/bankingRule/customerSpecificConditions"
}
]
}