Everything you need to put ResidenceVertical property reports in front of your own users.
ResidenceVertical sells a premium verification report for Romanian residential property — developer identity and litigation history, seismic-risk registry matches, building permits at the address, real comparable prices, neighbourhood signals. One report, one price, delivered as a PDF and as a web page.
This repository is for developers and product owners at a partner company — a real-estate portal, agency or broker network — integrating that report into their own product.
| GUIDE.md | The integration guide. The referral program, its two integration tiers, every endpoint, the commission and the weekly payout. Start at §1. |
| docs/ | The same guide as a PDF, if you would rather read or circulate it that way (rendered from GUIDE.md by docs/build-pdf.py). |
| sample/ | A runnable reference integration and a local mock of our API. Zero dependencies. |
| Live demo | A partner site we host, running against the real API. See the flow before you build it. |
There is a single partner program: referral. You send your users to our checkout, we handle payment, delivery and support, and you earn a commission (15% by default) on every report that generates — paid to you weekly by SEPA transfer, against your invoice to us. ResidenceVertical never charges a partner.
You can plug into it at either of two tiers, and both can be used on one account:
Link-only — a link to https://<env>/p/<your-slug> (optionally pre-filled with the
property address) placed on your site. No backend at all.
API-backed — your backend mints a checkout link per lead with one API call (exact
attribution, your own lead id on every conversion) and polls GET /referrals to learn
which leads converted. The recommended tier whenever you have a backend.
GUIDE.md §1 compares them side by side.
The sample ships with a local mock of the Partner API, so you can build and test the whole integration — minting checkout links, the public resolve, a stand-in checkout landing, the referral ledger and your payout reconciliation — before we issue you anything.
cd sample
node mock-rv-api.js # the mock API, port 4010
node server.js # the reference partner site, port 4000 (second terminal)Then open http://localhost:4000. No API key, no network, no npm install — Node.js 20+
built-ins only. node --test runs the sample's own suite.
See sample/README.md for the full walkthrough.
We host a working partner site — Portal Imobiliar Demo — built on this exact API:
https://gamma.residencevertical.ro/partner-demo
It is a fictional property portal with three listings. Clicking "Vezi raportul
ResidenceVertical" calls POST /checkout-links from its own backend with a real API key,
then sends you to our checkout with the address already filled in and the partner
attribution attached. Its "Conversiile mele" panel reads back live from
GET /referrals, so you can watch a lead turn into an attributed conversion.
In other words: the same flow as sample/, running against the real API rather
than a mock — useful for seeing what your users will experience before you build anything.
Access: the test environment is restricted to the ResidenceVertical team and to partners we have onboarded. Tell us at onboarding and we will enable your address, then this link works in your browser. The API itself (
/api/partner) is open to your test key from the moment you have one — see GUIDE.md §4.4.
Partner accounts are provisioned by us, per environment. Contact partners@residencevertical.ro with your company details and intended integration tier, and we will issue a test key plus a testing environment to point it at.
Keys are rvp_test_… (testing) and rvp_live_… (production). They are server-side only —
never ship one to a browser, a mobile app, or a public repository.
- Becoming a partner / key requests / payout details — partners@residencevertical.ro. Include your company, which tier you want, rough expected volume, and your payout details (IBAN, account holder, the company details for your commission invoices). You get back a test key and an environment to point at.
- A call failing in an existing integration — support@residencevertical.ro. Include
your partner slug and the
externalReference,referralIdorX-RV-Request-Id; it makes tracing a single request much faster. - Security — see SECURITY.md.
This repo contains the partner-facing integration guide and a reference sample. It is not the ResidenceVertical platform source, and the sample is illustrative — production-shaped (per-lead tracking, retries, error handling) but written to be read and adapted, not deployed as-is.
The API contract is versioned; breaking changes get a new version and advance notice. See the changelog at the end of GUIDE.md.