villagely
Integrations

What Villagely already talks to.

A short list, honestly labelled. Everything under “Working today” is live in the product right now; everything under “On the way” is not, and says so.

Working today

Four connections, all in production.

Stripe

Rent, dues and payouts

Bank transfer and card payments through Stripe Connect. Each organisation holds its own connected account, so money moves from your resident to your bank without sitting with us. Payouts, refunds and disputes stay in Stripe's own dashboard.

Email delivery

Invites, receipts and reminders

Transactional email is built in — resident invitations, payment receipts, rent reminders, maintenance updates and owner statements. Nothing to configure and no third-party account to hold.

The v1 REST API

Your data in your own systems

A read-only JSON API over properties, units, residents, leases, the ledger, maintenance and listings — bearer keys, org-scoped, 120 requests a minute. Access is by application.

1099-NEC export

For your accountant, or an IRIS upload

Contractor totals for the tax year download as a CSV from the 1099s screen, in the shape an accountant or an IRIS filing actually wants. Wider CSV export across the ledger and residents is not built yet — the API covers that today.

On the way

Not built yet.

Listed so you can plan around the gap rather than discover it. No dates, because a date we miss is worse than no date at all.

Tenant screening

Credit, criminal and eviction reports through a screening partner, with the applicant pushing their own report so the regulated data never passes through us.

Accounting exports

A journal export shaped for QuickBooks and Xero, so the books you keep here reconcile with the books your accountant keeps there.

More payment rails

Additional processors for organisations that already have a merchant relationship they would rather keep.

Build your own

If it isn’t on this page, the API probably covers it.

Most of what people ask for here is really “get my data into something else”, and that is what the v1 REST API is for — seven read-only resources, bearer keys, and a response shape that will not move under you. Access is by application so we can answer questions properly rather than leave you reverse-engineering it.

Read the API reference

Need something specific?

What customers ask for is what gets built next, in roughly the order they ask. Tell us what you are trying to connect and what it costs you today to do it by hand.

hello@villagely.io

Fourteen days free. No card.

Rent, leasing, maintenance, the association and the books — one system, set up in an afternoon.