Skip to content

Knowledgebase

Create a domain-operation quote and keep its currency and expiry attached to the order

domain-nexus, development

A Domain Nexus price quote records the evaluated price for a specific domain operation. Keep the quote reference with the customer order and use the same action, period and currency when submitting the corresponding operation.

01 Prepare the request

Check the domain and the account's offered TLDs first. For registration, availability and registry requirements are separate prerequisites. A quote does not reserve the name or guarantee that the provider will accept an otherwise ineligible operation.

API request example
POST /v2/pricing/quote
{
  "domain": "example.com",
  "action": "register",
  "years": 1
}

Send a valid Idempotency-Key. The route uses pricing:quote scope. Optional fields include currency_id, promo_code, reward_points and the documented premium input. Omit currency only when using the account's intended default.

02 Review the result

  1. Check the returned action, domain, period and currency.
  2. Review the actual amount and any applicable promotion or reward calculation.
  3. Store the quote identifier and its expiry with the order.
  4. Present the amount and terms clearly to your customer before a paid operation.
  5. Pass the appropriate price_quote_id when the registration, transfer, renewal or restore workflow requires it.

The handler bounds a requested period, but the TLD may support fewer terms. Do not assume a valid integer means the registry offers that registration length.

03 Handle premium names accurately

The quote's premium input is stored input, not an independent live registry premium-price check. Read availability and current provider data, and follow the premium acceptance workflow actually offered. Never manufacture a premium purchase approval solely from a client-side flag.

What should I do when a price quote expires or its inputs change?

Use GET /v2/pricing/quotes/{quoteId} to read an owned stored quote. If the price or eligibility must be refreshed, obtain a new quote and review the changed amount before submitting. Do not silently replace a customer's agreed amount with a higher price.

If a paid operation times out, inspect its original operation and quote before creating another. A new quote does not make repeating an uncertain renewal safe. Keep the local order, quote, idempotency key and provider result linked for reconciliation.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support