Grupo Zap Integration

Instead of a broker or agent re-typing the same listing into ZAP Imóveis, Viva Real and OLX separately, the property management system generates one standardized XML file and Grupo ZAP's crawlers pull it on a fixed schedule. Any change made once in the source system — a new price, an updated photo set, a listing marked as sold or rented — propagates automatically to every connected portal on the next crawl, which is the core reason agencies automate this instead of managing each portal's back office by hand.

Grupo ZAP's developer documentation names two supported XML schemas: the legacy "ZAP" format, which it explicitly describes as being in maintenance mode, and VRSync, the current standard that "incorporates all new functionality." The documentation states that non-VRSync feeds were being phased out, and Grupo ZAP's own XML validator tool only accepts VRSync-formatted files. Any new integration — including one built with a feed management tool — should target VRSync rather than the older format.

Grupo ZAP ingests listings through a polling architecture: it does not accept pushed uploads, it periodically downloads a VRSync XML file from a URL you provide. Per the official Guia de Conexão (connection guideline), the receiving server has to meet several concrete technical requirements:

1. Allow the crawler's User-Agent (identified in the documentation as VivaRealBot/1.0) or requests will fail with an HTTP 403
2. Serve the feed over HTTPS with a valid, non-self-signed certificate, supporting TLS 1.0–1.2
3. Respond within a 60-second connection timeout and complete the file transfer within a 20-minute download window
4. Keep the feed URL itself under 255 characters, using proper URL encoding with no raw spaces
5. Support up to 100 same-protocol redirects if the URL chain redirects

The official XML Validator additionally caps accepted files at 30MB and will reject anything not formatted as VRSync.

The VRSync schema is organized into a Listing block and a nested Details block. Based on Grupo ZAP's own element reference, the following are documented as required (or conditionally required by property type):

Feedance can generate and host the VRSync XML file that Grupo ZAP's crawler polls, mapping property records from your source system (CRM, ERP, or spreadsheet) into the Header, Listing and Details structure the standard requires.

1. Map your property data fields (address, price, bedrooms, bathrooms, area, photos, transaction type) to the corresponding VRSync elements
2. Configure the required conditional logic — for example, only populate LotArea for land listings, or RentalPrice only for Rent/Sale-Rent listings — since VRSync's required fields vary by property type
3. Publish the feed at a stable HTTPS URL that meets Grupo ZAP's connection requirements (valid certificate, User-Agent allowed, URL under 255 characters)
4. Register that feed URL with Grupo ZAP through Canal Pro or your account representative so their crawler begins polling it
5. Monitor the integration reports Grupo ZAP sends back (via Canal Pro, email or webhook, per their documentation) and correct any rejected listings at the source

Because this is a specialized, deeply nested real-estate schema rather than a flat product catalog, expect more upfront field-mapping work than with a standard e-commerce shopping feed.

Grupo ZAP's own documentation states that XML files are processed twice daily, at roughly 12-hour intervals — this is a crawl-based pull, not a push, so there is no benefit to regenerating the feed more frequently than that cycle. What matters is that the feed reflects current reality (price, availability, sold/rented status) before each crawl window, since a stale feed will keep an unavailable property listed, or an updated price un-synced, until the next 12-hour pull.

Grupo ZAP's documentation and its XML Validator flag several recurring causes of listing rejection:

1. Monetary and area values formatted with currency symbols, thousands separators or decimals — e.g. "R$560.000,00" or "32,20" — instead of plain integers
2. Missing the required currency="BRL" attribute on price elements, or the unit="square metres" attribute on area elements
3. Empty or missing Description elements (<Description/>), or descriptions outside the 50–3,000 character range
4. Missing LivingArea (or LotArea for land/farm listings), which the validator treats as a hard error
5. HTTP 403 responses because the hosting server blocks the crawler's User-Agent
6. Feed URLs exceeding 255 characters or containing unencoded characters/spaces
7. Files that are not valid VRSync XML, or exceed the 30MB validator limit

General feed-quality practices (not Grupo ZAP–specific claims) that tend to improve listing performance on real estate portals:

1. Go beyond the 5-image minimum — more photos, in a logical order with the exterior or best room first, typically improve engagement on listing portals
2. Write complete, accurate descriptions that use the full available character range rather than the minimum, since a thin 50-character description is unlikely to convert well even if it passes validation
3. Keep price and status fields synchronized with your source system in real time on your end, so the next crawl always pulls current data rather than a stale snapshot
4. Fill in optional differentiators where available (virtual tour links, precise latitude/longitude, neighborhood/zone detail) to help buyers filter and find the listing

Does Feedance support the VRSync format specifically? Feedance can generate XML feeds mapped to the VRSync element structure that Grupo ZAP's documentation defines; the legacy ZAP format is deprecated and should not be used for new integrations.

Can I send the same feed to ZAP Imóveis, Viva Real and OLX? Grupo ZAP's own materials describe a single XML feed being distributed to the portals included in your contracted plan, rather than requiring separate feeds per portal.

How will I know if a listing was rejected? Grupo ZAP states it sends integration reports and, for errors persisting more than three days, direct email notifications with details on what failed.

Is this the same kind of feed as a Google Merchant Center or Meta product feed? No — VRSync is a real-estate-specific schema with nested Location, Media, ContactInfo and Details structures and property-type-dependent required fields, which is structurally different from a flat e-commerce product feed, even though the underlying goal (one source feed, multiple destinations) is similar.