KOBBLE_KYB_2 company whose owners the verification partner cannot discover from a registry (for example a UAE company), declare them yourself and have Kobble verify each one. Declare the owners as stakeholders on the enduser company (POST /customers/v1/endusers/{id}/stakeholders, or nested at enduser creation) with at least one of the roles DIRECTOR, UBO or SHAREHOLDER, then call this endpoint. Each ACTIVE such stakeholder becomes a type: KYC / subject_type: EXTERNAL_PARTY party verification linked to the company with source CUSTOMER and source_ref = the stakeholder id, appears in the company's links_from[], gates the KYB aggregate like a partner-discovered party, and can be given its hosted link with GET /customers/v1/verifications/{party_id}/session-token or emailed it with POST /customers/v1/verifications/{companyId}/parties/{partyId}/invite.PARTNER) parties, and closed (REJECTED / CANCELLED) companies gain no parties. Should the partner later deliver registry owners for a company with declared owners, both sets are kept and the company is flagged reason_code DECLARED_OWNERS_REVIEW for a Kobble officer, without a status change.links_from[]. Requires the client/write scope. Owner-scoped.