Featured image showing the Naver Map Open API Authentication Failed (200) issue and the parameter change to ncpKeyId

Even though the service URL was correctly registered in the application settings, authentication still fails.

Problem: Naver Map authentication fails

Naver Map Open API authentication failed. Please check the client ID and web service URL., * Error Code / Error Message: 200 / Authentication Failed, * Client ID: xxxxx, * URI: http://localhost:8030/xxxxx

Authentication Failed (200) error message shown in the browser

Application settings screen with the service URL correctly registered

Cause: The client ID parameter name changed from ncpClientId to ncpKeyId

Reference document

Solution: Use the correct parameter ID

Before the change

1<!-- 일반 -->
2<script type="text/javascript" src="https://oapi.map.naver.com/openapi/v3/maps.js?ncpClientId=YOUR_CLIENT_ID"></script>
3
4<!-- 공공 -->
5<script type="text/javascript" src="https://oapi.map.naver.com/openapi/v3/maps.js?govClientId=YOUR_CLIENT_ID"></script>
6
7<!-- 금융 -->
8<script type="text/javascript" src="https://oapi.map.naver.com/openapi/v3/maps.js?finClientId=YOUR_CLIENT_ID"></script>

After the change

1<!-- 개인/일반 통합 -->
2<script type="text/javascript" src="https://oapi.map.naver.com/openapi/v3/maps.js?ncpKeyId=YOUR_CLIENT_ID"></script>

Why Did It Change

The consoles that were previously separated for public institutions and financial institutions have been integrated into a single console for individuals/general businesses. The parameters were also consolidated into one to match.

CategoryPrevious ParameterAfter Change
Individual/GeneralncpClientIdncpKeyId
Public InstitutiongovClientIdncpKeyId
Financial InstitutionfinClientIdncpKeyId

It has been announced that the existing consoles for public institutions and financial institutions will be discontinued. If you were using those consoles, you need to issue a new key from the integrated console.

⚠️ Since different documents were updated at different times, some pages still refer to the old parameter name. It is more reliable to check the script loading method based on the Maps JavaScript API v3 Getting Started documentation.

Web Service URL Registration Rules

If the same error occurs even after fixing the parameter, check the web service URL registered in the console.

Only the host domain should be registered; the port number and URI must be excluded.

Incorrect RegistrationCorrect Registration
http://localhost:8080http://localhost
http://127.0.0.1/mainhttp://127.0.0.1

If the URI shown in the earlier error message was in the form http://localhost:8030/hospitals/..., also check whether the registered value includes a port or path.

Checklist

  1. Check whether the parameter in the loading URL is ncpKeyId.
  2. Check whether the key was issued from the integrated console. Authentication fails if you continue to use a key from the old console.
  3. Remove the port number and path from the registered web service URL.
  4. The previous script may be cached, so clear the browser cache and check again.

Reference