NiceNIC 도메인 API v2 자주 묻는 질문

NiceNIC 도메인 API v2 is an HTTPS 및 JSON-based API f또는 automating 도메인 management through 귀하의 NiceNIC account.

It supp또는ts c또는e w또는kflows including 도메인 availability checks, registration, renewal, transfer, p또는tfolio queries, nameserver 및 contact updates, pricing, DNS rec또는ds, child nameservers, account inf또는mation 및 compliance-related operations.

Use the API when you want to connect NiceNIC 도메인 서비스s directly to a website, hosting platf또는m, billing system, internal tool 또는 other application.

Any active NiceNIC account can use 도메인 API v2. API access is 사용 가능 to both 마켓 계정s 및 리셀러 계정s.

You do not need to become a reseller simply to obtain API access. 계정 type still matters f또는 pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request.

열기 API 설정s →

예. API access itself is free. T여기 is no separate fee f또는 enabling API access 또는 sending supp또는ted API requests.

Paid operations such as 도메인 registration, renewal 및 transfer are charged acc또는ding to 귀하의 account pricing 및 the applicable 도메인 rules.

아니요. API access 및 reseller pricing are separate.

You can use 도메인 API v2 with a regular NiceNIC 마켓 계정. 업그레이드 a 리셀러 계정 only when reseller pricing 또는 other reseller benefits are useful f또는 귀하의 business volume.

Compare 리셀러 Plans →

도메인 API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication 및 documentation 또는ganized around individual 도메인 및 account w또는kflows.

만약 you maintain an integration built on an older NiceNIC API, review the API v2 parameters 및 response h및ling bef또는e migrating production traffic rather than assuming the two versions are interchangeable.

로그인 to 귀하의 NiceNIC account 및 open API 설정s. API v2 requests use 귀하의 NiceNIC username 및 API Secret f또는 authentication.

열기 API 설정s →

예. NiceNIC provides an API S및box f또는 developers to test integrations bef또는e connecting them to the production API.

Use the S및box to validate authentication, request f또는matting, response parsing, 오류 h및ling 및 귀하의 application w또는kflow bef또는e enabling live customer 도메인 operations.

열기 API S및box →

The API S및box is intended f또는 development 및 integration testing. The 상품ion API is used f또는 live 도메인 operations 및 paid requests against 귀하의 NiceNIC account.

We recommend validating authentication, request h및ling, response processing 및 오류 logic in the S및box bef또는e enabling customer-facing production operations.

Send API requests over HTTPS 및 include 귀하의 NiceNIC username 및 API Secret in the Authorization header.

Host: api.nicenic.net
Authorization: username:api_secret
Content-Type: application/json

만약 IP restrictions are enabled f또는 귀하의 account, requests must also 또는iginate from an auth또는ized server IP.

Read API 인증 →

The 상품ion API base endpoint is:

https://api.nicenic.net/v2/

API 작업s are selected using the parameters documented f또는 each endpoint, such as category 및 action. Always follow the dedicated endpoint documentation f또는 the required 및 optional parameters of a specific operation.

API v2 responses use JSON, 및 request parameters use UTF-8.

{
  "code": 0,
  "msg": "success",
  "data": {}
}

Your application should inspect the returned code 및 msg rather than assuming that every HTTP response represents a completed 도메인 operation.

Through the currently documented APIs you can automate w또는kflows including 도메인 availability checks, registration, renewal 및 transfer, p또는tfolio listing 및 도메인 details, nameserver 및 도메인 contact updates, 도메인 pricing, DNS rec또는ds, child nameservers, account inf또는mation 및 남용 및 준수 monit또는ing.

추가itional w또는kflows are documented individually in the API navigation.

Start with low-risk read operations such as 도메인 availability, 도메인 pricing, account balance 및 도메인 listing.

Then confirm authentication, response parsing, 오류 h및ling 및 pending-또는der h및ling bef또는e enabling live registrations, renewals 또는 transfers.

예. The 도메인 가용성 확인 endpoint supp또는ts multiple 도메인 names separated by commas.

example.com,example.net,example.org

Do not assume that every API operation supp또는ts the same multi-도메인 input f또는mat. 등록, renewal 및 transfer should follow their individual endpoint documentation.

Use the 도메인 가격 보기 endpoint. The documented pricing types include register, renew, transfer 및 all.

등록 responses can also include an is_premium value indicating whether the queried registration is premium.

Because API 또는ders use account-level pricing, query current pricing bef또는e submitting paid customer 또는ders rather than relying indefinitely on cached prices.

아니요. Although API documentation supp또는ts periods of up to 1–10 년 f또는 applicable extensions, individual TLDs may have different registry rules.

등록 periods, renewal periods, transfer eligibility, contact requirements 및 verification requirements can differ by extension. Your application should follow the current rules f또는 the relevant TLD.

These are separate operations 및 should not be treated as interchangeable.

Always use the returned code 및 message when determining the state of an API request.

View API 응답 코드 →

A 201 response means that the operation has been accepted f또는 processing but has not necessarily reached its final state.

F또는 도메인 registration, a 201 response indicates that the 또는der has been submitted 및 is awaiting final registry processing.

Do not tell an end customer that the 도메인 is active until 귀하의 system has confirmed the final result. 팔로우 the registration endpoint documentation f또는 the latest pending-또는der 및 refund h및ling rules.

A pending transfer means that the transfer request has been accepted f또는 processing, not that the 도메인 has already completed its transfer to NiceNIC.

이전 completion may depend on registry 및 registrar processing as well as the current transfer status of the 도메인. Keep the transfer in a pending state until completion is confirmed.

예. The 목록 도메인 API supp또는ts p또는tfolio retrieval with pagination, s또는ting 및 filtering options.

Use 받기 도메인 상세 내용 when you need detailed inf또는mation f또는 an individual 도메인, such as registration inf또는mation, expiration inf또는mation, nameservers 및 도메인 contact data.

NiceNIC 도메인 API v2 includes 남용 및 준수 operations designed f또는 platf또는ms 및 resellers managing customer 도메인 p또는tfolios.

You can identify 도메인s associated with abuse rep또는ts 및 retrieve machine-readable compliance inf또는mation f또는 individual 도메인s. Depending on the case, the response can include 도메인 status, current impact, recommended 작업, hold inf또는mation, complaint inf또는mation 및 rep또는ted URLs.

This makes it possible to surface compliance status directly inside 귀하의 own customer p또는tal 또는 operational system.

예. NiceNIC provides a WHMCS registrar integration f또는 businesses that already use WHMCS f또는 billing 및 provisioning.

Use the direct 도메인 API v2 when you are building 귀하의 own application 또는 w또는kflow. Use the WHMCS integration when you want 도메인 operations integrated into an existing WHMCS environment.

View WHMCS 연동 →

Any server-side programming language 또는 runtime capable of sending HTTPS requests 및 parsing JSON can integrate with 도메인 API v2.

Common choices include PHP, Python, 아니요de.js 및 Java. Keep API credentials server-side 및 never expose 귀하의 API Secret in browser-side JavaScript 또는 downloadable client code.

평점 limiting may be applied to protect API stability 및 platf또는m security.

만약 귀하의 production integration is expected to generate sustained high request volume, contact NiceNIC bef또는e launch so that 귀하의 expected usage pattern can be reviewed.

Include the request timestamp, API 카테고리 및 작업, 도메인 name w여기 applicable, non-sensitive request parameters, returned response code 및 message, 및 whether the request came from S및box 또는 상품ion.

티켓 제출 →

Use the API navigation in the documentation. Each operation has its own page f또는 supp또는ted parameters, request examples, response examples 및 operation-specific behavi또는.

The FAQ explains general API behavi또는; the individual endpoint documentation should be treated as the source of truth f또는 the exact request f또는mat.

열기 API 문서 →