Integrate your CRM

Your CRM stays the home of your portfolio. You can connect ImobyFlow to it without code, using the same file it sends to the listing portals, or code the sync field by field through the API.

Two paths

No code — the feed link. ImobyFlow reads the XML your CRM already generates for ZAP Imóveis and Viva Real (VRSync format), every 6 hours. This is the path for properties.
With code — the API. Your code reads the CRM and writes here, using the CRM’s own property code. This is the path when the feed is not enough: clients, interactions, or properties updated right away.

One source per account for properties. With the feed on, it rules the portfolio: a property that disappears from the XML is taken down after 36 hours. That is why the API does not write properties for that account (it answers feed_sync_active). Status and availability confirmation remain allowed, and so do clients.

No code: the feed link

Ask your CRM support for the link to the XML it generates for ZAP Imóveis and Viva Real. If the CRM generates one file per portal, use the one for these two — that is the VRSync format.
In the ImobyFlow dashboard, add the link under Properties › Import › CRM sync. The screen shows how each read ended.
Done: the read repeats every 6 hours. To skip the wait, your system calls POST /v1/feed/sync when the portfolio changes, and GET /v1/feed shows how it ended.

What you edit in ImobyFlow is not overwritten by the feed: if the CRM later changes the same field, the dashboard asks which value to keep.

With code: the field map

Every CRM that publishes to ZAP Imóveis and Viva Real uses the same format, VRSync. This is the map from each of its tags to the API field — exactly what ImobyFlow does when it reads the feed. Write with PUT /v1/properties/by-ref/{code}: the same call creates or updates. For many at once, use POST /v1/properties/batch (up to 500).

In VRSync	In the API	Notes
`ListingID`	`externalRef`	The property code in the CRM. In `PUT /v1/properties/by-ref/{code}` it goes in the path — that is what makes the same call create or update.
`Title`	`title`	HTML markup is stripped.
`TransactionType`	`purposes`	`For Sale` → `VENDA`, `For Rent` → `LOCACAO`, `Sale/Rent` → both.
`Details/PropertyType`	`type`	Becomes a subtype: `Residential / Apartment` → `APARTAMENTO`, `Residential / Home` → `CASA_RUA`, `Residential / Condo` → `CASA_CONDOMINIO` (a house in a gated community, in VRSync), `Commercial / Land Lot` → `TERRENO_RUA`.
`Details/ListPrice`	`salePrice`	In rent-only listings the CRM usually puts the rent here: send it as `rentPrice`.
`Details/RentalPrice`	`rentPrice`	The rent, when the listing is also for rent.
`Details/LivingArea`	`area`	The total private area, in m² — the one the Radar compares.
`Details/LotArea`	—	This is the LOT area. It only becomes `area` for land and rural; for an apartment, sending it as `area` would advertise the size of the whole building lot.
`Details/Bedrooms`	`bedrooms`	Bedrooms.
`Details/Bathrooms`	`bathrooms`	Bathrooms.
`Details/Garage`	`parkingSpots`	Parking spots.
`Details/Description`	`description`	`<br>` and `</p>` become line breaks; other markup is stripped.
`Details/PropertyAdministrationFee`	—	The condo fee. The API has no field for it yet; through the feed it comes in.
`Location/City`	`address.city`	Together with `address.state` (the UF from `Location/State`). Or send only `address.cityId`, the IBGE code.
`Location/State`	`address.state`	The UF comes in the `abbreviation` attribute.
`Location/Neighborhood`	`address.neighborhood`	Goes through the alias dictionary. An unrecognized neighborhood waits for curation, and the property stays out of recommendations until then.
`Location/Address`	`address.street`	Street.
`Location/StreetNumber`	`address.number`	Number.
`Location/Complement`	`address.complement`	Complement.
`DetailViewUrl`	`listingUrl`	The listing on the agency's website.
`Media/Item`	`photos`	Only `medium="image"` (videos are left out). The one with `primary="true"` goes first — the 1st in the list is the cover. Up to 30.

Clients have no common format across CRMs: read the client from your CRM’s API and write it with PUT /v1/leads/by-ref/{code}, using the client code from the CRM.

Your CRM

What each CRM's public documentation says, checked in October 2026. CRMs change: their documentation outranks this page. Trademarks belong to their owners and appear here only to identify each system.

Kenlo
The simplest path
If your listings reach ZAP Imóveis and Viva Real through the CRM, it already generates an XML in the VRSync format: ask the support for that link and add it to ImobyFlow.
The CRM's API
The Kenlo API is private: homologated partners only, and Kenlo itself warns that unofficial integrations may be blocked.
Access
Through the Kenlo "Integre conosco" program, with validation.
CRM documentation
Vista (Loft CRM)
The simplest path
If your listings reach ZAP Imóveis and Viva Real through the CRM, it already generates an XML in the VRSync format: ask the support for that link and add it to ImobyFlow.
The CRM's API
The key goes in the URL, on a host specific to each customer (*.vistahost.com.br). It lists and details properties and clients, 50 per page, and only returns the fields requested in fields. No change notifications are documented: your code polls periodically.
Access
Through a ticket in the Vista Service Center. There is a public test key to try it out.
CRM documentation
Jetimob
The simplest path
If your listings reach ZAP Imóveis and Viva Real through the CRM, it already generates an XML in the VRSync format: ask the support for that link and add it to ImobyFlow.
The CRM's API
The key goes in the URL path. It lists properties by date window, and Jetimob itself recommends a full read every 30 minutes and an incremental one every 5. It has no webhooks of its own (it uses Zapier or Make).
Access
With a Jetimob plan that includes access to API keys.
CRM documentation
Imobzi
The simplest path
This is the CRM where the API pays off the most: it sends a webhook when a property or contact is created, changed or deleted, with the full record. Your code receives it and writes here right away.
The CRM's API
The key goes in the X-Imobzi-Secret header. Contacts, properties, deals and rentals, with a downloadable OpenAPI specification.
Access
On the Imobzi CRM Business or Rental plans.
CRM documentation
Superlógica
The simplest path
If your listings reach ZAP Imóveis and Viva Real through the CRM, it already generates an XML in the VRSync format: ask the support for that link and add it to ImobyFlow.
The CRM's API
The Superlógica API covers rentals, billing and condominiums. The credentials (app_token and access_token) belong to a system user and last one year: if that person leaves the agency, the integration stops.
Access
Through the system user, as described in the Superlógica help center.
CRM documentation
CV CRM
The simplest path
This is the developers' CRM. The developer connects CV CRM in the ImobyFlow dashboard (Developments › CV CRM) and each unit type's sales map updates on its own, every hour: available, reserved and sold units, and the "from" price. No code.
The CRM's API
The key goes in headers (e-mail and token), on a host specific to each customer. Limit of 200 calls per minute (20 for bulk loads); going over blocks for 1 minute.
Access
Granted by contract with CV CRM.
CRM documentation