Skip to main content
Sienge is a comprehensive ERP platform for the construction industry, offering a suite of tools for managing projects, financials, supplies, and more. It helps streamline operations and provides valuable insights for construction companies.

​
API Types: Bulk vs Transactional

Sienge provides two types of APIs with different capabilities and permission requirements:
Bulk API - Used for extracting large volumes of historical data. Requires enabling Massive endpoints in your API token configuration.Transactional API - Used for extracting master data and transactional records. Requires standard API permissions for each resource.
Make sure your API token has the appropriate permissions enabled for the streams you want to extract. See the Sienge API documentation for details on configuring API permissions.

​
Configuring Sienge as a Source

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

​
1. Add account access

The following configurations are available:
  • API User: The user to authenticate against the API service. Check this documentation on how to create it.
  • API Password: The password to authenticate against the API service.
  • Company Domain: The domain identifier for your company account. For example, if your Sienge workspace URL is https://mycompany.sienge.com.br, then your company subdomain would be mycompany.
  • Company ID: The ID of the company to sync (use 1 if you don’t know).
  • Building IDs: The IDs of the buildings you want to extract data, used in the Building Resources stream.
  • Enterprise IDs: The IDs of the enterprises you want to extract sales data from.
  • Start date: The earliest record date to sync.
For Bulk streams, you must enable permission to extract bulk data from the API, usually referred to as Massive in the token configuration. You have to enable all Massive endpoints. Check the official documentation for guidance.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. The streams available are related to the different modules in Sienge. 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. Read more about Sync Types here.
Once you are done configuring, click Next.

​
4. Configure data source

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. 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. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
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 Sienge, organized by API type.

​
Transactional Streams

These streams use the Transactional API and require standard API permissions for each resource. They are typically used for master data and reference tables.
Stream containing chart of accounts information.Fields:
Stream containing daily account balance information.Fields:
Stream containing building project calendar and working-day settings per enterprise.Fields:
Stream containing checking account information.Fields:
Stream containing company information.Fields:
Stream containing cost center information.Fields:
Stream containing creditor/supplier information.Fields:
Stream containing customer information with detailed personal and company data.Fields:
Stream containing enterprise/project information.Fields:
Stream containing inventory movements and stock transactions.Fields:
Stream containing payment category/financial category information.Fields:
Stream containing transactional purchase order information.Fields:
Stream containing stock inventory information for cost centers.Fields:
Stream containing supply contract information, filtered by start and end date.Fields:
Stream containing detailed item information for supply contract measurements.Fields:
Stream containing items for supply contract measurements.Fields:
  • documentId: String - Identifier of the document
  • contractNumber: String - Contract number
  • buildingId: String - Building ID (primary key)
  • measurementNumber: String - Measurement number (primary key)
  • itemId: String - Item ID (primary key)
Stream containing stock reservation information.Fields:
Stream containing building units information and their specific settings.Fields:

​
Bulk Streams

These streams use the Bulk API and require Massive endpoint permissions in your API token configuration. They are designed for extracting large volumes of data efficiently.
Stream for managing sales information and customer relationships. Requires enterprise_ids configuration.Fields:
Stream containing income and receipt information.Fields:
Stream for managing business budget information.Fields:
Stream containing accounting balances for cost centers.Fields:
Stream with detailed information about invoice items.Fields:
Stream for managing bills from defaulter customers.Fields:
Stream containing bank movement and transaction data.Fields:
Stream for customer debt balance information.Fields:
Stream for items in building cost estimations.Fields:
Stream containing accounting balances for companies.Fields:
Stream containing outcome and payment information.Fields:
Stream for managing building resources. Requires building_ids configuration.Fields:
Stream for the history of customer extracts.Fields:
Stream for managing purchase quotations.Fields:

​
Implementation Notes

​
API Limits & Performance

  • Rate Limiting: Sienge enforces an account-wide limit of 200 requests per minute across all streams. To prevent bursting past this limit—especially during large backfills or when multiple streams are syncing in parallel—the connector automatically paces requests. For example, daily paginated streams like Accounts Balances introduce a slight delay (0.6 seconds) between requests to stay safely under the API quota. The same pacing is applied to other high-volume streams, such as Supply Contracts Measurement Items, to prevent rate limiting errors (HTTP 429).

​
Skills for agents

Download Sienge skills file

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