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ドキュメント →