Using the regcity API

Use the regcity API to check availability, register, renew and manage domains from your own scripts, with the same prices and balance as the control panel.

1. Get your API key

Open Profile → API Key and click Generate a New Key. Keep the key secret: anyone who has it can spend your account balance. If it leaks, generate a new one; the old key stops working immediately.

2. How requests work

• Base URL: https://regcity.net/api
• Every call is POST https://regcity.net/api/<role>/<module>/<method> with a JSON body.
• role is guest for public calls (no key) or client for calls on your account.
• Client calls use HTTP Basic authentication: username client, password your API key.

curl -s -u client:YOUR_API_KEY \
  -H 'Content-Type: application/json' \
  -X POST https://regcity.net/api/client/client/balance_get_total

Every response has the same shape:

{"result": 25.4, "error": null}

On failure result is null and error holds message and code. Authentication Failed means the key is wrong, reset or missing. Requests are rate-limited; if you get a rate-limit error, wait and retry.

3. Check availability and prices (no key needed)

curl -s -H 'Content-Type: application/json' -X POST \
  https://regcity.net/api/guest/domaincheck/check \
  -d '{"sld": "example", "tld": ".com"}'

4. Before you register: contact and nameservers

Registration uses your default domain contact and your default nameservers.

Fill in missing contact details in Profile in the control panel.

5. Register domains

curl -s -u client:YOUR_API_KEY -H 'Content-Type: application/json' -X POST \
  https://regcity.net/api/client/bulkdomain/register \
  -d '{"domains": ["example.com", "example.net"], "years": 1, "ns1": "ns1.example.org", "ns2": "ns2.example.org"}'

• domains: an array, or a string with one domain per line; up to 200 per request.
• years: registration period (default 1).
• ns1–ns4: optional; without them your default nameservers are used.
• contact_id: optional; without it your default contact is used.

Availability is not checked here. Check the domains first (section 3).

The call returns at once: {"batch_id": 12, "queued": 2, "errors": {}}. The orders are then placed in the background and one invoice is issued for the whole batch. It is paid from your balance automatically if the balance is enough; otherwise it stays unpaid, and you can pay it in Invoices. Domains are registered within a few minutes of payment.

Follow progress with client/bulkdomain/batches ({}): each batch shows ordered, waiting, failed, the errors per domain and invoice_hash. If a domain cannot be registered after payment, its cost is returned to your balance.

6. Renew domains

curl -s -u client:YOUR_API_KEY -H 'Content-Type: application/json' -X POST \
  https://regcity.net/api/client/bulkdomain/renew \
  -d '{"domains": ["example.com", "example.net"]}'

Renews every listed domain that is active in your account for one more period, on a single invoice paid from your balance when possible. Returns renewed, errors (for example, a domain that is not yours or already has an unpaid renewal invoice) and invoice_hash.

7. Change nameservers

curl -s -u client:YOUR_API_KEY -H 'Content-Type: application/json' -X POST \
  https://regcity.net/api/client/bulkdomain/update_nameservers \
  -d '{"domains": ["example.com"], "ns1": "ns1.example.org", "ns2": "ns2.example.org"}'

Only domains in your account are changed. The change is sent to the registrar within a few minutes; check the result with client/bulkdomain/jobs ({}).

8. Your domains, balance and invoices

Single-domain actions take the order ID from client/order/get_list:

Need help?

Open a ticket in Support and include the call you made and the full error response. Never include your API key.