Question 1

NiceNIC 도메인 API v2란 무엇인가요?

Accepted Answer

NiceNIC Domain API v2 is an HTTPS and JSON-based API for automating domain management through your NiceNIC account. It supports core workflows including domain availability checks, registration, renewal, transfer, portfolio queries, nameserver and contact updates, pricing, DNS records, child nameservers, account information and compliance-related operations. Use the API when you want to connect NiceNIC domain services directly to a website, hosting platform, billing system, internal tool or other application.

Question 2

누가 NiceNIC 도메인 API v2를 사용할 수 있나요?

Accepted Answer

Any active NiceNIC account can use Domain API v2. API access is available to both Market Accounts and Reseller Accounts. You do not need to become a reseller simply to obtain API access. Account type still matters for pricing: paid API operations use the pricing assigned to the NiceNIC account sending the request. Open API Settings →

Question 3

NiceNIC 도메인 API v2는 무료인가요?

Accepted Answer

Yes. API access itself is free. There is no separate fee for enabling API access or sending supported API requests. Paid operations such as domain registration, renewal and transfer are charged according to your account pricing and the applicable domain rules.

Question 4

API를 사용하려면 리셀러 계정이 필요한가요?

Accepted Answer

No. API access and reseller pricing are separate. You can use Domain API v2 with a regular NiceNIC Market Account. Upgrade to a Reseller Account only when reseller pricing or other reseller benefits are useful for your business volume. Compare Reseller Plans →

Question 5

API v2는 기존 NiceNIC API와 어떻게 다른가요?

Accepted Answer

Domain API v2 uses the current NiceNIC API structure with HTTPS requests, JSON responses, header-based authentication and documentation organized around individual domain and account workflows. If you maintain an integration built on an older NiceNIC API, review the API v2 parameters and response handling before migrating production traffic rather than assuming the two versions are interchangeable.

Question 6

API 자격 증명은 어떻게 받나요?

Accepted Answer

Sign in to your NiceNIC account and open API Settings. API v2 requests use your NiceNIC username and API Secret for authentication. Security tip: Keep your API Secret on the server side. Do not expose it in browser-side JavaScript, public repositories, client applications or other publicly accessible locations. Open API Settings →

Question 7

NiceNIC 도메인 API v2에서 API 샌드박스를 제공하나요?

Accepted Answer

Yes. NiceNIC provides an API Sandbox for developers to test integrations before connecting them to the production API. Use the Sandbox to validate authentication, request formatting, response parsing, error handling and your application workflow before enabling live customer domain operations. Open API Sandbox →

Question 8

샌드박스와 프로덕션 API의 차이점은 무엇인가요?

Accepted Answer

The API Sandbox is intended for development and integration testing. The Production API is used for live domain operations and paid requests against your NiceNIC account. We recommend validating authentication, request handling, response processing and error logic in the Sandbox before enabling customer-facing production operations.

Question 9

API 인증은 어떻게 작동하나요?

Accepted Answer

Send API requests over HTTPS and include your NiceNIC username and API Secret in the Authorization header. Host: api.nicenic.net Authorization: username:api_secret Content-Type: application/json If IP restrictions are enabled for your account, requests must also originate from an authorized server IP. Read API Authentication →

Question 10

도메인 API v2는 어떤 엔드포인트를 사용하나요?

Accepted Answer

The Production API base endpoint is: https://api.nicenic.net/v2/ API actions are selected using the parameters documented for each endpoint, such as category and action. Always follow the dedicated endpoint documentation for the required and optional parameters of a specific operation.

Question 11

API v2는 어떤 응답 형식과 문자 인코딩을 사용하나요?

Accepted Answer

API v2 responses use JSON, and request parameters use UTF-8. { "code": 0, "msg": "success", "data": {} } Your application should inspect the returned code and msg rather than assuming that every HTTP response represents a completed domain operation.

Question 12

NiceNIC 도메인 API v2로 무엇을 할 수 있나요?

Accepted Answer

Through the currently documented APIs you can automate workflows including domain availability checks, registration, renewal and transfer, portfolio listing and domain details, nameserver and domain contact updates, domain pricing, DNS records, child nameservers, account information and Abuse & Compliance monitoring. Additional workflows are documented individually in the API navigation.

Question 13

실제 등록 또는 이전을 활성화하기 전에 무엇을 테스트해야 하나요?

Accepted Answer

Start with low-risk read operations such as domain availability, domain pricing, account balance and domain listing. Then confirm authentication, response parsing, error handling and pending-order handling before enabling live registrations, renewals or transfers. Recommended order: Authentication → Availability → Pricing → Balance → Response handling → Live operations.

Question 14

하나의 API 요청으로 여러 도메인을 확인할 수 있나요?

Accepted Answer

Yes. The Check Domain Availability endpoint supports multiple domain names separated by commas. example.com,example.net,example.org Do not assume that every API operation supports the same multi-domain input format. Registration, renewal and transfer should follow their individual endpoint documentation.

Question 15

등록, 갱신 및 이전 가격을 어떻게 조회할 수 있나요?

Accepted Answer

Use the Get Domain Pricing endpoint. The documented pricing types include register, renew, transfer and all. Registration responses can also include an is_premium value indicating whether the queried registration is premium. Because API orders use account-level pricing, query current pricing before submitting paid customer orders rather than relying indefinitely on cached prices.

Question 16

모든 TLD를 1~10년 동안 등록하거나 갱신할 수 있나요?

Accepted Answer

No. Although API documentation supports periods of up to 1–10 years for applicable extensions, individual TLDs may have different registry rules. Registration periods, renewal periods, transfer eligibility, contact requirements and verification requirements can differ by extension. Your application should follow the current rules for the relevant TLD.

Question 17

네임서버, DNS 레코드 및 하위 네임서버의 차이점은 무엇인가요?

Accepted Answer

NameserversDetermine where a domain's authoritative DNS is delegated. DNS RecordsManage records inside a DNS zone when using NiceNIC DNS services. Child NameserversCreate host/glue records such as ns1.example.com. These are separate operations and should not be treated as interchangeable.

Question 18

API 응답 코드는 무엇을 의미하나요?

Accepted Answer

CodeMeaning 0Success 201Pending 400Parameter error 401Unauthorized 404No relevant records found 500Server Internal Error Always use the returned code and message when determining the state of an API request. View API Response Codes →

Question 19

코드 201은 무엇을 의미하나요?

Accepted Answer

A 201 response means that the operation has been accepted for processing but has not necessarily reached its final state. Important: Do not treat a pending response as final success. Preserve the pending state until the final result of the domain operation is confirmed.

Question 20

도메인 등록 시 코드 201이 반환되면 어떻게 되나요?

Accepted Answer

For domain registration, a 201 response indicates that the order has been submitted and is awaiting final registry processing. Do not tell an end customer that the domain is active until your system has confirmed the final result. Follow the registration endpoint documentation for the latest pending-order and refund handling rules.

Question 21

전송 보류(Pending transfer) 응답은 무엇을 의미하나요?

Accepted Answer

A pending transfer means that the transfer request has been accepted for processing, not that the domain has already completed its transfer to NiceNIC. Transfer completion may depend on registry and registrar processing as well as the current transfer status of the domain. Keep the transfer in a pending state until completion is confirmed.

Question 22

API를 통해 도메인 포트폴리오를 조회하고 필터링할 수 있나요?

Accepted Answer

Yes. The List Domains API supports portfolio retrieval with pagination, sorting and filtering options. Use Get Domain Details when you need detailed information for an individual domain, such as registration information, expiration information, nameservers and domain contact data.

Question 23

신고 및 규정 준수 API는 무엇을 할 수 있나요?

Accepted Answer

NiceNIC Domain API v2 includes Abuse & Compliance operations designed for platforms and resellers managing customer domain portfolios. You can identify domains associated with abuse reports and retrieve machine-readable compliance information for individual domains. Depending on the case, the response can include domain status, current impact, recommended action, hold information, complaint information and reported URLs. This makes it possible to surface compliance status directly inside your own customer portal or operational system.

Question 24

NiceNIC 도메인 API v2를 WHMCS와 함께 사용할 수 있나요?

Accepted Answer

Yes. NiceNIC provides a WHMCS registrar integration for businesses that already use WHMCS for billing and provisioning. Use the direct Domain API v2 when you are building your own application or workflow. Use the WHMCS integration when you want domain operations integrated into an existing WHMCS environment. View WHMCS Integration →

Question 25

어떤 프로그래밍 언어를 사용할 수 있나요?

Accepted Answer

Any server-side programming language or runtime capable of sending HTTPS requests and parsing JSON can integrate with Domain API v2. Common choices include PHP, Python, Node.js and Java. Keep API credentials server-side and never expose your API Secret in browser-side JavaScript or downloadable client code.

Question 26

API 요청 속도 제한이 있나요?

Accepted Answer

Rate limiting may be applied to protect API stability and platform security. If your production integration is expected to generate sustained high request volume, contact NiceNIC before launch so that your expected usage pattern can be reviewed.

Question 27

API 문제로 지원팀에 문의할 때 무엇을 포함해야 하나요?

Accepted Answer

Include the request timestamp, API category and action, domain name where applicable, non-sensitive request parameters, returned response code and message, and whether the request came from Sandbox or Production. Never include your full API Secret in a normal support ticket. Submit a Ticket →

Question 28

전체 요청 매개변수와 코드 예제는 어디에서 찾을 수 있나요?

Accepted Answer

Use the API navigation in the documentation. Each operation has its own page for supported parameters, request examples, response examples and operation-specific behavior. The FAQ explains general API behavior; the individual endpoint documentation should be treated as the source of truth for the exact request format. Open API Documentation →

코드	의미
`0`	성공
`201`	대기 중
`400`	매개변수 오류
`401`	인증 실패
`404`	관련 레코드를 찾을 수 없습니다
`500`	서버 내부 오류

도메인 찾기

도메인 찾기 및 등록

도메인 이전

조회 및 보호

도메인 작업 자동화

시작하기

연동 및 확장

리셀러 가격으로 성장하기

리셀러 솔루션

비즈니스 필수

워크플로우 연결

무엇을 도와드릴까요?

셀프 서비스

고객 지원

결제 및 전문 채널

구매 전 NiceNIC 인증하기

회사 및 증명

신뢰와 투명성

계정 액세스

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

시작하기

샌드박스 및 인증

도메인 작업 및 가격

응답 및 오류

포트폴리오, 규정 준수 및 통합

개발 및 지원

지금 바로 구축을 시작할 준비가 되셨나요?