Skip to main content
Imoview is a property management and real estate CRM platform that supports rental and sale workflows, tenant and guarantor contracts, inspections, condominiums, and client (user) data. Data is extracted via the Imoview API using an API key (chave) and optional email/senha for app endpoints that require user context.

​
Configuring Imoview as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Imoview option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your Imoview API credentials so Nekt can access your data. The following configurations are available:
  • API key: API key (chave) for the Imoview API. The access key is provided by UNIVERSAL SOFTWARE.
  • Email: Imoview user email. When provided together with Password, Nekt uses it to obtain codigoacesso and codigoUsuario via the app validation endpoint. This is required for streams that use App_ endpoints (e.g. client_companies, rental_contracts).
  • Password: Imoview user password. Used with Email to authenticate and retrieve app credentials for App_ endpoints.
  • Start date: Records created or updated after the start date will be extracted from the source. Used for the first full sync and for incremental syncs when supported by the stream.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data), and the type of sync.
  • Layer: Choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: A folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: We suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: You can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: Every time the extraction happens, we’ll get only the new or updated data. Supported for clients, rental_contracts, and condominiums where the API supports replication by date.
    • Full table: Every time the extraction happens, we’ll get the current state of the data.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync.
Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

Below you’ll find all available data streams from Imoview and their corresponding fields:
Stream for clients (locador, locatário, proprietário, comprador, fiador). Source: RetornarTipo3.
Stream for rental contracts. Source: Locacao/RetornarContratos.
Stream for companies from Imoview CRM. Source: Cliente/App_RetornarEmpresas. Requires email and senha for app credentials.
Stream for available condominiums. Source: Imovel/RetornarCondominiosDisponiveis (POST).
Stream for available rental properties (finalidade=1). Source: Imovel/RetornarImoveisDisponiveis (POST).
Stream for available properties for sale (finalidade=2). Same endpoint as Properties Rent with finalidade=2.Key Fields: Same structure as Properties Rent (codigo, condomínio, título, tipo, situação, valor, endereço, quartos, áreas, datas, fotos, etc.).

​
Data Model

The following diagram illustrates the relationships between the data streams in Imoview. Clients is the main entity; rental_contracts are filtered by client role (locatário). Client companies, condominiums, properties_rent, and properties_sale are independent streams.

​
Implementation Notes

​
Authentication

  • For client_companies and rental_contracts, the tap calls the app validation endpoint with email and senha (MD5) to obtain codigoacesso and codigoUsuario, which are then sent in headers or params as required by the API.

​
Replication

  • Clients supports incremental sync via dataultimaalteracao (filter dataHoraInicialUltimaAlteracao).
  • Rental contracts and condominiums support replication by their respective date fields where the API allows.

​
Pagination

  • Streams use page-based pagination (numeroPagina / numeroRegistros). Page size is 100 for all streams.

​
Resilience

  • The connector implements retry logic for transient errors and unauthorized responses.
  • App credentials are automatically refreshed when needed with a 30-minute TTL.
  • Record cleansing is applied to ensure data consistency with day-first date format.

​
Skills for agents

Download Imoview skills file

Imoview connector documentation as plain markdown, for use in AI agent contexts.