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.

​
1. Add your UAU access

  1. 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.
  2. Click Next and you’ll be prompted to fill the configuration.
    • 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/developer token, sent in the X-INTEGRATION-Authorization header. It is obtained from the UAU developer registration and must be authorized by your company for this integration.
    • Login: The UAU user login used to authenticate against the API.
    • Password: The password for that UAU user.
    • 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.
  3. Click Next.

​
2. Select your UAU streams

  1. The next step is letting us know which streams you want to bring. You can select entire groups of streams or only a subset of them.
    Tip: The stream can be found more easily by typing its name.
  2. Click Next.

​
3. Configure your UAU data streams

  1. 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. Read more about Sync Types here.
  2. Click Next.

​
4. Configure your UAU data source

  1. Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
  2. To define your Trigger, consider how often you want data to be extracted from this source.
  3. Optionally, you can define some additional settings (if available).
    • 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.

​
Check your new source!

  1. Click Next to finalize the setup. Once completed, you’ll receive confirmation that your new source is set up!
  2. You can view your new source on the Sources page. Now, for you to be able to see it on your Catalog, you have to wait for the pipeline to run. If needed, manually trigger the pipeline by clicking on the refresh icon.
If you encounter any issues, reach out to us, and we’ll gladly assist you!

​
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:
  • Codigo_emp: Integer - Unique company (empresa) code
  • Desc_emp: String - Company name / description
  • CGC_emp: String - Company CNPJ (federal tax ID)
  • IE_emp: String - State registration (Inscrição Estadual)
  • InscrMunic_emp: String - Municipal registration (Inscrição Municipal)
  • Endereco_emp: String - Company address
  • Fone_emp: String - Company phone number
Active construction projects registered in UAU (Obras/ObterObrasAtivas). Synced as a full table.Fields:
  • Cod_obr: String - Construction project (obra) code
  • Empresa_obr: Integer - Company (empresa) code that owns the obra
  • Descr_obr: String - Obra description / name
  • Status_obr: Integer - Obra status code
  • Ender_obr: String - Obra address
  • Fone_obr: String - Obra phone number
  • Fisc_obr: String - Fiscal obra code
  • DtIni_obr: DateTime - Obra start date
  • Dtfim_obr: DateTime - Obra end date
  • TipoObra_obr: Integer - Obra type code
  • EnderEntr_obr: String - Obra delivery address
  • CEI_obr: String - Obra CEI (INSS registration) code
  • DataCad_obr: DateTime - Obra registration timestamp
  • DataAlt_obr: DateTime - Obra last-change timestamp
  • UsrCad_obr: String - User who registered the obra
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:
  • codigo_empresa: Integer - Company (empresa) code of the sale
  • codigo_obra: String - Construction project (obra) code of the sale
  • numero_venda: Integer - Sale (venda) number, unique within empresa + obra
  • data_referencia: DateTime - Upper bound of the queried period (sync reference time), used as the incremental replication key
  • raw: String - Original key object returned by the API, serialized as a JSON string
Financial summary of each sale, computed as of the sync date, fetched per venda (Venda/ConsultarResumoVenda).Fields:
  • codigoEmpresa: Integer - Company code of the sale
  • codigoObra: String - Obra code of the sale
  • numeroVenda: Integer - Sale (venda) number
  • dataCalculo: DateTime - Date the summary was calculated
  • totalParcelas: Integer - Total number of installments
  • totalDesconto: Number - Total discounts of the sale
  • totalAPagarComDesconto: Number - Total payable with discounts applied
  • parcelasportipo: Array of Objects - Installment totals broken down by installment type
    • tipoParcela: String - Installment type code
    • descricaoTipoParcela: String - Installment type description
    • quantidadeParcelaAPagar: Integer - Number of installments still to pay
    • totalParcelaAPagar: Number - Total amount of installments still to pay
    • quantidadeParcelaPaga: Integer - Number of installments already paid
    • totalParcelaPaga: Number - Total amount of installments already paid
  • totaisareceber: Array of Objects - Totals of amounts still to be received (outstanding balance, principal, interest, correction, penalty, late interest, overdue counts, etc.)
  • totaisrecebido: Array of Objects - Totals of amounts already received (total received, principal, interest, correction, discounts, early/late counts, etc.)
  • descontoantecipacao: Object - Anticipation-discount campaign applied to the sale (campaign code and description, discount percentage and type)