List contract prices
The prices agreed with one customer alone. A contract rule that fits a purchase and is in date beats everything on the customer's price list.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
id*stringSuccess
application/json- response
Success
data*array<>curl -X GET "https://example.com/v1/customers/cus_01K6XJ4Q8ZT3M9R5V2B7WDHNCA/contract-rules"{ "data": [ { "id": "prr_01K6XJ4Q8ZT3M9R5V2B7WDHNCA", "product": "number", "match": "com", "term": "30d", "action": "new", "minQuantity": 10, "kind": "markup", "value": 2500, "startsAt": "2026-10-07T11:04:31.000Z", "endsAt": "2027-10-07T00:00:00.000Z" } ]}Preview a price change POST
Takes the changes you are thinking of making to a list and saves nothing. Says how many customers are on the list and, for up to 50 of the domains, licences and numbers they hold, what one unit of the next renewal costs them now and what it would cost after the change.
Replace contract prices PUT
Replaces the whole set; send an empty list to clear it. Rules have the same shape as price list rules, with optional dates. `add` and `fixed` values are in the currency of the customer's list. Two rules for the same items and tier must not be in date at the same time.