Skip to main content
UAU (by Globaltec/Senior) is an ERP built for the construction and real-estate development industry (construtoras, incorporadoras, and imobiliárias). It manages companies, construction projects (obras), sales (vendas), receivables, and financials.
UAU is self-hosted: each customer runs its own UAU Web API instance. You must provide the base URL of your installation (the “Caminho WebService” shown in the UAU portal) and it must be reachable from Nekt. There is no shared/public environment.

​
Configuring UAU as a Source

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

​
1. Add account access

Provide the necessary credentials to authenticate with your self-hosted UAU instance. The following configurations are available:
  • API Base URL: The base URL of your UAU Web API, for example https://uauapi.yourcompany.com.br. This is the “Caminho WebService” available in the UAU portal under your user settings. Make sure it is reachable from the internet.
  • Integration Token: The integration token for the UAU API, sent in the X-INTEGRATION-Authorization header. It is issued by UAU/Senior for your installation, obtained from your own developer registration or provided by UAU/Senior support for your environment.
  • Login: The UAU user login used to authenticate against the API.
  • Password: The password for that UAU user.
  • Empresas: Optional list of UAU empresa codes to extract, e.g. 1, 2. Leave it empty to extract every empresa your UAU installation returns. Use it when the installation is shared by a group of companies and your UAU user only has permission on some of them.
  • UAU Site User (Advanced): An optional UAUSite user, sent on login as UsuarioUAUSite.
  • Start date (Advanced): The earliest record date to sync (used by the incremental Vendas stream).
  • Verify SSL Certificate (Advanced): Verify the server’s TLS certificate. Disable only for trusted self-hosted UAU servers with an incomplete certificate chain.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. 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: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data. Recommended for streams like Vendas.
    • Full table: every time the extraction happens, we’ll get the current state of the data. Used for streams like Empresas and Obras.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization. To define your Trigger, consider how often you want data to be extracted from this source (e.g., daily, hourly). 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. This will complement incremental data extractions, ensuring that your data is completely synchronized with your source periodically.
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 UAU.
Active companies registered in UAU (Empresa/ObterEmpresasAtivas). Synced as a full table.Fields:
Active construction projects registered in UAU (Obras/ObterObrasAtivas). Synced as a full table.Fields:
Keys of the sales inserted or changed within a period, fetched per obra (Venda/RetornaChavesVendasPorPeriodo). Synced incrementally: each run queries the period since the previous sync.Fields:
Financial summary of each sale, computed as of the sync date, fetched per venda (Venda/ConsultarResumoVenda).Fields:

​
Implementation Notes

​
Shared Installations & Permission Denials

UAU’s top-level endpoints list every empresa of the installation, ignoring user permission grants. This means a customer sharing their UAU base with a larger corporate group will inevitably query companies they cannot read.
  • Child streams (e.g., vendas): If UAU denies access (returning a 401 Unauthorized “não tem acesso” error) to a specific empresa or obra, the connector will log a warning and automatically skip that partition. The sync will continue successfully for the data you can access.
  • Root streams (e.g., empresas): Permission denials on top-level streams will fail the extraction to prevent silent data loss (e.g., yielding no records and overwriting an entire table as empty).
To avoid querying unauthorized empresas altogether and speed up your extractions, explicitly list your allowed codes in the Empresas configuration setting.