Ask for a product line
Asks for a product line (numbers, domains or licences) to be switched on for this account. Product lines are turned on by the platform; this records the ask, with when it was made, for the team to act on. Asking again keeps the first date. Refused with product_already_on for a line the account can already order.
apiKeyAuthorizationBearer <token>An API key from the Developers page. rhq_test_ keys reach the sandbox, rhq_live_ keys the live side.
application/json- body
product*string"domains""numbers""licences"Success
application/json- response
Success
product*string"domains""numbers""licences"requestedAt*stringdate-timecurl -X POST "https://example.com/v1/account/product-requests" \ -H "Content-Type: application/json" \ -d '{ "product": "domains" }'{ "product": "domains", "requestedAt": "2019-08-24T14:15:22Z"}Update billing details PATCH
How your account is identified on invoices, and the defaults a new invoice falls back to when `dueInDays`, `taxBps` or `note` is not given. Send only what changes; `null` clears a field. Live and sandbox keep their own.
Bring sandbox setup to live POST
Copies what was set up while trying the account in the sandbox to live, for the parts asked for: `prices` (every price list, with its rules), `portal` (the customer portal’s branding and content, published and draft) and `business` (the details printed on invoices). Once, before live has sold anything; refused with `live_in_use` after. Never overwrites: a part live already has is left as it is, and the response says which parts were copied. Promotions, customers and which customer is on which list stay behind, as sandbox customers are not live ones.