ViveSol Connect for Estatik

Automatically publish your Estatik property listings on ViveSol.es and give them greater visibility. Reach new potential clients and drive more visitors to your website without spending extra time managing your properties, thanks to our corporate real estate network.

Features include:

• Native mapping for Estatik 4.x fields: operation, property type, price, bedrooms, bathrooms, floor area, images, location and featured labels.
• Province lookup from Estatik’s es_location hierarchy (administrative_area_level_2).
• Mandatory province validation before sending a listing. Listings without a province are not published and are shown as errors. A default province can be configured as a fallback.
• Mapping for pool, garage, elevator, terrace and air conditioning from Estatik features, amenities and parking taxonomies.
• Background synchronization queue, bounded retries for temporary failures and safe bulk synchronization in batches.
• Per-listing synchronization status and a local event log retained for 90 days.
• Built-in Spanish quick-start guide, troubleshooting notes and a link to the ViveSol help center.
• Remote deletion when a property is moved to the trash or permanently deleted, plus re-synchronization after restoration.

Requirements

• WordPress 5.8 or later.
• PHP 7.2 or later.
• An active Estatik installation. The connector supports Estatik 4.x, whose property post type is properties.
• An active ViveSol API key associated with the agency.

External service

This plugin connects to the ViveSol API at https://vivesol.es to create, update and remove property listings in the ViveSol.es real estate network. ViveSol is an external service that provides the remote listing publication functionality.

The API connection is disabled by default. It is only used after a site administrator enables the connection, accepts the publishing agreement and enters a valid API key in the plugin settings.

ViveSol also offers an optional assisted connection process. After the administrator expressly accepts publication and authorizes ViveSol from their own WordPress dashboard, the service uses a temporary WordPress Application Password to install or activate this plugin and configure the API key, default province, connection and consent settings. The administrator’s normal WordPress password is never shared with ViveSol. The connector does not store the Application Password, and its authenticated status endpoint returns only whether an API key is saved, never the key itself.

When synchronization is enabled, the plugin sends the information needed to publish a listing, which may include:

• Source website and property URLs, WordPress property ID, title or reference.
• Property operation, type, price, bedrooms, bathrooms, floor area, description, location, coordinates, features and publication status.
• Property image URLs.
• Contact phone number, email address and WhatsApp number configured for the property or agency.

ViveSol terms of service: https://vivesol.es/terminos-del-servicio/

ViveSol privacy policy: https://vivesol.es/politica-de-privacidad/

Province and location

Estatik 4 stores Country, State, Province and City as terms in its hierarchical es_location taxonomy. The connector first uses Province, then a term with the administrative_area_level_2 type, and only then State or the configured default province.

Province is required for a listing to appear on ViveSol.es. If it cannot be determined, the property remains unpublished and is marked as an error in Vivesol Connect for Estatik > Properties with an actionable explanation.

Synchronization and monitoring

Estatik changes are queued shortly after saving so all metadata is available and the editor remains responsive. WordPress runs these tasks through WP-Cron. The initial import runs in batches of five listings. If WP-Cron is disabled on the hosting environment, the Synchronization screen provides a “Process next batch now” button.

The Properties tab filters synchronized, failed and pending listings, and can retry an individual listing. The Log tab keeps the previous 90 days of events. API keys and response bodies are never recorded in this log.