Onboarding Questionnaire - Public

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

Changed on

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.

get/public/onboarding-questionnaire/{token}/nipc-lookup

Request

  • Base URL
    https://api.multigest.pt (the document declares no server; this is the origin it was published from)
  • URL
    https://api.multigest.pt/public/onboarding-questionnaire/{token}/nipc-lookup
  • Auth
    API key in header x-api-token and API key in header x-origin-verify

Path parameters

tokenstring required

Query parameters

nipcstring required

PT NIPC, 9 digits

Response

Successful Response

unknown required

Changes