---
title: "Suggest registry data (VIES) for a NIPC the client typed"
method: GET
path: "/public/onboarding-questionnaire/{token}/nipc-lookup"
tags: ["Onboarding Questionnaire - Public"]
---

# Suggest registry data (VIES) for a NIPC the client typed

`GET /public/onboarding-questionnaire/{token}/nipc-lookup`

Resolve a NIPC into the registered name + sede address, as a SUGGESTION.

`async def` on purpose (redesign §8.2): the only slow part is the outbound
VIES HTTP call, which is awaited (never pins a threadpool worker); the two
small DB/Redis touches are pushed to the threadpool. Every failure mode —
VIES down, masked data, checksum-invalid NIPC, over-capacity — degrades to
`{"available": false}` / `{"found": false}` and the form simply shows
nothing: this endpoint must never be the reason a dealer cannot type.

## Path parameters

- `token` string, required

## Query parameters

- `nipc` string, required — PT NIPC, 9 digits

## Response `200`

Successful Response

- unknown

## Other responses

- `422` — Validation Error

## Changes

- **2026-09-02** `8492136eefc5` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/multigest/apis/multigest-protected-api/changes/public/onboarding-questionnaire/:token/nipc-lookup/get.md)

---

[API](https://skmtc.dev/multigest/apis/multigest-protected-api.md) · [All operations](https://skmtc.dev/multigest/apis/multigest-protected-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/multigest/multigest-protected-api/revisions/ace841cc41cc/schema)