KYB Registry Select
Retrieve the full registry profile of one candidate returned by POST /v3/kyb/search/ — company details, officers, beneficial owners, addresses, industries, filings, and the complete raw registry payload.
Pairing with search. Pass the candidate’s kyb_response_id exactly as returned by the search. The handle is ephemeral and scoped to that search — select promptly, and re-search for a fresh handle rather than storing it.
Billing. Each select is billed at the KYB registry price (search is free). The balance is checked before any registry call (403 when short) and the charge is recorded against the created business session.
Persistence is mandatory. Every select creates a business session (its id is the request_id) so billing and retrieval can be tracked; it appears in the console. save_api_request is accepted for symmetry but must be true (the default) — sending false returns 400.
Resolution. The API polls the registry for the full profile before responding. If the registry is still processing after polling, the response comes back with fetch_status: "pending" / data_resolved: false and sparse fields; the stored record completes automatically once the registry resolves (the business session status updates with it) — re-check it in the Business Console or by polling GET /v3/session/{request_id}/decision/ (business sessions resolve through the same decision endpoint).
Status. kyb_registry.status is Didit’s assessment of the registry check: companies that are not active in the registry, or whose officers/ownership could not be derived, are routed to In Review; clean active companies are Approved. registry_status is the company’s own status at the registry (e.g. active, dissolved).
Sandbox. Keys from sandbox applications return a static resolved company without contacting any registry and without billing.
POST /v3/kyb/search/ returns candidate companies.
Selecting a company is billable. It retrieves the full registry profile, stores the request as a Manual Check in the Business Console, and returns a request_id you can use to retrieve the saved business verification result.
Didit waits for the source registry to finish before responding, so fetch_status is resolved in most responses. If a slow registry keeps the profile pending past that wait, the response returns fetch_status: pending with data_resolved: false, and Didit completes the saved check automatically as soon as the provider finishes — re-read the saved verification result instead of repeating the search, since a new search issues new kyb_response_id values.Authorizations
Body
Candidate handle from POST /v3/kyb/search/ (kyb_registry.companies[].kyb_response_id). Ephemeral — use it shortly after the search that produced it.
255"69aeeb95febb0f1704042259"
Your identifier for this company; echoed back and stored with the business session.
Free-form JSON stored with the business session and echoed back.
Must be true (the default). KYB registry selects are always persisted so billing and retrieval can be tracked; false returns 400.
Response
Company retrieved and billed. kyb_registry carries the full profile; check data_resolved — when false the registry was still processing and the stored record completes automatically once it resolves.
Id of the business session created for this retrieval. The stored record (visible in the console) keeps updating if the registry resolves after the response.
Full registry company profile.
Echo of the vendor_data you sent.
Echo of the metadata you sent.