The two checks
Owner-KYC (once per person)
Prove who you are with an identity document. Approval grants the
OWNER role.Property proof (once per property)
Prove your right to list a specific property. Approval publishes it.
Becoming an owner (KYC)
1
Apply
POST /api/v1/verification/kyc opens a request (any signed-in user).2
Attach your ID
Upload the document via the media endpoints, then attach it with role
SELF_ID
(POST /api/v1/verification/kyc/{id}/documents). Capture its expiry date — an expired ID
is rejected at submit.3
Submit
POST /api/v1/verification/kyc/{id}/submit puts it in the review queue.4
Admin approves
An administrator approves it. You are granted the
OWNER role and your own organization;
sign in again to get a token carrying the new role and org_id.Listing a property
Once you are anOWNER:
1
Register the property
POST /api/v1/properties creates it in DRAFT (not yet visible to tenants).2
Open a right-to-list proof
POST /api/v1/verification/property-proofs with the propertyId and a proofType:
OWNERSHIP (you own it — attach an attestation) or MANDATE (you manage it for the
owner — attach the signed mandate + the owner’s ID).3
Submit and get reviewed
Submit it; a manager or administrator approves. On approval the property flips to
PUBLISHED automatically.Reviews, decisions and revocation
- Reviewers can approve, reject, or request more information (you resubmit).
- Owner-KYC is decided by
ADMIN; property proofs byMANAGERorADMIN. - An administrator can revoke an approval later (fraud): revoking owner-KYC strips the
OWNERrole and withdraws the owner’s published properties; revoking a property proof withdraws that property.
docs/06-owner-onboarding-and-verification.md); this page is the API-user
view.
