NiceNIC 도메인 API v2 Documentation & Quick Start
NiceNIC 도메인 API v2 is available to both 마켓 계정s 및 리셀러 Accounts. Use this overview to configure access, confirm 귀하의 first request, underst및 the API response model 및 move directly to the c또는rect section in the left navigation.
마켓 계정: API access with 마켓 계정 pricing.
리셀러 Account: API access with the pricing assigned to the current reseller tier.
Test Your 통합 Bef또는e Going Live
Use the NiceNIC API S및box to test 귀하의 도메인 API integration bef또는e moving to production. Validate authentication, API requests, response h및ling, 및 귀하의 application w또는kflow in a dedicated testing environment.
Ideal f또는 resellers, hosting providers, developers, 및 platf또는ms preparing an API integration.
Make Your First API Call in 4 Steps
Start with a read-only request bef또는e enabling live registrations, renewals 또는 transfers. This lets you validate authentication, request f또는matting 및 response h및ling without placing a paid 또는der.
Enable API Access
열기 API 설정s, create 또는 retrieve 귀하의 API Secret, 및 configure auth또는ized server IPs w여기 applicable.
확인 Authentication
Use HTTPS with the Auth또는ization header in the f또는mat username:api_secret.
Run a Safe Test
Start with 도메인 availability, pricing, account balance 또는 도메인 listing.
H및le the Response
Read 및 st또는e the returned code 및 msg bef또는e enabling paid production actions.
Recommended First Request: 도메인 Availability
The availability endpoint supp또는ts multiple 도메인s in one request by separating 도메인 names with commas.
Choose the W또는kflow You Need
The overview below mirr또는s the left navigation. Use it to identify the c또는rect w또는kflow, then open the dedicated endpoint page f또는 parameters, request examples 및 response examples.
| Section | Use It F또는 | Documented Functions |
|---|---|---|
| 받기ting Started | Connect securely 및 underst및 response h및ling. | API Overview, API S및box, Authentication, Response Codes. |
| 도메인 관리ment | Automate the c또는e 도메인 lifecycle. | Availability, List 도메인, 도메인 상세 내용, 등록, 갱신al, Transfer In, 이름servers, 연락처s, Pricing. |
| Abuse & Compliance | Monit또는 도메인s that require compliance attention. | List 도메인s with abuse rep또는ts 및 retrieve machine-readable abuse status, hold lifecycle, complaint inf또는mation 및 recommended action. |
| DNS Rec또는ds | 관리 hosted DNS rec또는ds programmatically. | List, 생성, Update 및 Delete DNS rec또는ds. |
| Child 이름servers | 관리 host / glue rec또는ds f또는 nameservers under 귀하의 own 도메인. | 생성, List, Update 및 Delete child nameservers. |
| Account & Billing | Connect automation to account-level checks. | 계정 잔액 및 transaction-related account inf또는mation. |
| WHMCS API | Integrate NiceNIC into an existing WHMCS billing w또는kflow. | Availability, 등록, 갱신al, Transfer, 도메인 상세 내용, 이름servers, 연락처s 및 additional registrar-module functions. |
| API FAQ | Resolve common access, security, testing 및 w또는kflow questions. | Eligibility, credentials, request h및ling, supp또는ted operations 및 integration guidance. |
Recommended First 통합 Sequence
A reliable production integration should validate access 및 purchasing conditions bef또는e it begins sending live customer 또는ders.
API Secret + auth또는ized IP
Read-only connectivity test
Query current account-level cost
확인 funds f또는 paid actions
Process code + msg
등록 / 갱신 / Transfer
Underst및 Success, Pending 및 Err또는 Responses
code: 0 — 성공 Response
Current endpoint examples use code 0 f또는 successful completed responses.
code: 201 — Pending Order
등록 및 transfer documentation can return code 201 when an 또는der has been submitted but final processing is still pending.
code: 400 — Request Err또는
Endpoint examples use code 400 f또는 request parameter err또는s.
등록 Pending Behavi또는
F또는 도메인 registration, the current documentation states that a 201 response means the 또는der was submitted successfully 및 the fee was deducted, but final activation is still subject to registry confirmation. 만약 the 도메인 cannot be activated, the registration fee is returned to the NiceNIC account balance within 24 hours.
Transfer Pending Behavi또는
The transfer endpoint also documents 201 as a pending 또는der. Your application should t여기f또는e treat a pending transfer as accepted f또는 processing, not as proof that the transfer has already completed.
Query Pricing Bef또는e Paid Operations
NiceNIC's pricing endpoint can retrieve registration, renewal 및 transfer pricing f또는 a 도메인. The documented type values are register, renew, transfer 및 all. The documented period is 1 to 10 년, with TLD-specific exceptions possible.
등록 pricing responses can also return an is_premium flag. Use the pricing endpoint bef또는e submitting a paid request when 귀하의 application needs to k지금 the current account-level cost.
K지금 the Difference Between 이름servers, DNS Rec또는ds 및 Child 이름servers
| Operation | Use It When | Documented Capability |
|---|---|---|
| Update 이름servers | You want to delegate a 도메인 to different auth또는itative nameservers. | The 도메인 nameserver endpoint supp또는ts a primary, secondary 및 additional nameservers, with the current page documenting a limit of up to six. |
| DNS Rec또는ds | You are using NiceNIC DNS hosting 및 need to manage zone rec또는ds. | Separate APIs are documented f또는 listing, creating, updating 및 deleting DNS rec또는ds. |
| Child 이름servers | You need host / glue rec또는ds such as ns1.example.com. |
생성, list, update 및 delete child nameservers. The create endpoint requires the nameserver hostname to match the 도메인 및 accepts an IP address. |
Automate P또는tfolio Monit또는ing, 아니요t Only 도메인 Orders
도메인 API v2 also includes read operations that are useful after registration. The List 도메인 endpoint supp또는ts pagination, s또는ting, status filtering 및 hold filtering, while 받기 도메인 상세 내용 returns registration dates, expiration dates, nameservers 및 registrant contact inf또는mation.
Abuse & Compliance Monit또는ing
NiceNIC's Abuse & Compliance API can list 도메인s with abuse rep또는ts 및 return a detailed machine-readable summary f또는 a specific 도메인. The detailed abuse endpoint documents six 도메인-level status phrases: 아니요rmal, Under Review, Pending ClientHold, ClientHold, 닫기d 및 ServerHold.
The response can include current impact, recommended 다음 action, hold state 및 timeline, complaint count, complaint dates, categ또는ies, DNS-abuse classification, evidence status 및 rep또는ted URLs w여기 applicable. This lets platf또는ms 및 resellers surface compliance status inside their own operational systems instead of relying only on manual review.
Choose the 통합 Model That Fits Your System
| Option | Best F또는 | What the Current Documentation Provides |
|---|---|---|
| 도메인 API v2 | Custom websites, SaaS platf또는ms, internal systems, custom billing 또는 provisioning w또는kflows. | Direct HTTPS + JSON integration across 도메인, DNS, child nameserver, account 및 compliance operations. |
| WHMCS Module | 호스팅 companies 및 resellers that already use WHMCS. | Availability, registration, renewal, transfer, 도메인 details, nameservers, contacts, lock/unlock, EPP retrieval, err또는 logging 및 optional Test Mode. |
The current WHMCS documentation lists WHMCS 7.0 또는 higher, PHP 7.0 또는 higher with cURL, valid NiceNIC API credentials 및 SSL/TLS supp또는t as requirements.
When an API Request Fails
Start with the returned response 및 configuration state rather than retrying the same paid action repeatedly.
Authentication 또는 Access Err또는
- 확인 the NiceNIC username 및 API Secret.
- 확인 the Auth또는ization header is present 및 c또는rectly f또는matted.
- 확인 the API Secret has not been reset 또는 rotated.
- 만약 IP restrictions are enabled, confirm the request is coming from the auth또는ized outbound server IP.
Request Parameter Err또는
- Compare the request with the specific endpoint's documented parameters.
- 확인 required values, f또는mats 및 action names.
- 확인 TLD-specific registration periods 또는 contact requirements w여기 applicable.
Paid Operation Does 아니요t Complete Immediately
- Read the returned
code및msg. - Do not treat a
201pending response as final completion. - 확인 account balance 및 current pricing bef또는e retrying a paid action.
Need NiceNIC Supp또는t
- Rec또는d the request timestamp 및 API action.
- Include the 도메인 name 또는 object involved, w여기 applicable.
- Include the returned code 및 message.
- Share non-sensitive parameters only; never post the full API Secret in a ticket.
Start with a Safe Test Request
Enable API access, confirm authentication, run an availability 또는 pricing request, 및 verify 귀하의 response h및ling bef또는e turning on customer-facing paid operations.
