Yes, from day one. Screening runs from a shareable link, so nothing about your PMS changes and there is nothing to install. Native integrations with property management systems are planned and none are live yet; until they ship, links, the API, and exports carry the workflow.
Integrations and API
Keep your leasing workflow. Upgrade the screening layer.
The deep integration work is already done on Burnt's side. Applicants connect their payroll provider at the source, and partner reports arrive in the same package. Your side can start with a link, today.
No rip-and-replace. No IT ticket. No waiting on integrations.
Sources
Your stack
Payroll providersapplicant-connected
Identityverified at the source
Bank incomewhere payroll is thin
Partner reportscredit, background, eviction
Shareable linklive today
API + webhookslive today
Native PMSplanned
The source side
Wired by Burnt. Nothing for your team to build.
Payroll and income providers
Live
Identity verification
Live
Credit, background, and eviction partners
Live
Your side
Three live paths in, one planned.
Shareable screening links
Live
API and webhooks
Live
CSV and report exports
Live
Native PMS integrations
Planned
An integration has two sides.
The hard half is already wired. Burnt connects to the sources that prove income, employment, and identity, and to the FCRA-regulated partners that produce credit, background, and eviction reports. Your half can stay exactly as it is: links work with what you run today, and deeper hooks are planned, sequenced with your input.
What the API does.
Three capabilities cover the full loop, with no polling. Access is set up with the Burnt team rather than self-serve keys, so a working integration comes with a person attached.
POST /screenings
Create a screening request for a unit and an applicant.
screening.updated
Webhook events as consent, connections, and checks complete.
GET /screenings/:id/report
Pull the completed package into your system of record.
White-glove during beta.
Pick your connection path.
All three reach the same dashboard and the same package. The difference is who does the work and where results land.
| Shareable link | API + webhooks | Native PMS (planned) | |
|---|---|---|---|
| Time to first screening | Minutes | Days, with the Burnt team | When it ships |
| Engineering required | None | One short integration sprint | None once live |
| What flows automatically | Invites out, results in one dashboard | Requests, status events, completed reports | Screening inside the PMS |
| Best for | Starting today | Portfolios with their own systems | Teams that live in the PMS |
Short answer
Does Burnt integrate with property management systems?
Burnt works alongside any property management system from day one, because screening runs from a shareable link and nothing about the PMS changes: AppFolio, Yardi, Buildium, or anything else. An API with webhooks covers request creation, status events, and completed-report retrieval, and results export as CSV. Native PMS integrations are planned. On the source side the connections are already live: applicants link payroll providers directly, and credit, background, and eviction reports come from FCRA-regulated partners.
Frequently asked questions.
Send the link.
Guide the renter.
Review one package.
Launch with screening links or talk through a portfolio workflow with the Burnt team.
