Skip to main content
POST
Estimate pre-warmed domain cost

Authorizations

Authorization
string
header
required

Authenticate every request with a Bearer token. Pass your Reply API key in the Authorization header:

Get your API key from the Reply dashboard: Settings → API Key.

Body

application/json

Same shape and rules for the estimate and the purchase, so one body can be posted to both.

serviceProvider
enum<string>
required

Mailbox provider the bundle is listed with, case-insensitive. Must be the provider the domain was found under — a bundle is not visible to the other one.

Available options:
Google,
Microsoft
domain
object
required

Response

Price breakdown for the bundle

Every amount is in cents — 1299 means twelve dollars and ninety-nine cents.

currency
string
required

Currency the amounts are denominated in

domain
object
required

The domain being ordered and what it costs

mailboxSeats
EstimateSeats · object
required

Paid-seat counts and unit price for one seat type in an order estimate.

Example:
emailAccountSeats
EstimateSeats · object
required

Paid-seat counts and unit price for one seat type in an order estimate.

Example:
subtotal
integer<int64>
required

Amount due now, in cents — the domain price in full plus the added seats. The billing provider prorates each seat to the rest of the current billing term, so the seat part is usually not addedCount × unitPrice.

discount
number
required

Discount applied to the order. Currently always 0.

total
integer<int64>
required

Amount charged if the order is placed, in cents