Skip to main content
BTG Parceiros is a financial services platform designed for BTG Partners, which are offices or consultancy firms that offer and manage BTG products for their clients. It provides tools for financial data management, reporting, and client portfolio tracking for investment and wealth management services.
This source is available for BTG Partners only. Partners are offices or consultancy firms that offer and manage BTG products for their clients. This connector is not meant to be used for PJ or PF BTG accounts.

​
Configuring BTG Parceiros as a Source

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

​
1. Add account access

You will need to provide the following credentials:
  • Client ID: the client ID of the BTG Parceiros developer account.
  • Client secret: the client secret of the BTG Parceiros developer account.
These credentials can be generated from the Developer Partner portal.
  • Go to Autorização, then click on Gerar novas chaves
  • Store the new keys safely and use them to fill the required fields at Nekt
Besides generating the credentials, you’ll have to configure a webhook URL on the Webhooks -> Manutenção section. Please get in touch with Nekt support to get the webhook URL that should be used there. Once you’re done, click Next.

​
2. Select streams

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.
The streams available bring D-1 reports.
If you don’t see a stream you were expecting to find, please check if your access key has access to it. If that’s not the issue, then it’s probably because we still haven’t implemented it. Feel free to get in touch and request it!
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 (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. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
When you are ready, click Next to finalize the setup.

​
5. Check your new source

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. You can now monitor it on the Sources page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your new table will appear in the Catalog section.
For you to be able to see it on your Catalog, you need at least one successful source run.
If you encounter any issues, reach out to us via Slack, and we’ll gladly assist you!

​
Implementation Notes

  • Primary Keys: The connector safely handles records with missing composite primary key fields by generating a reliable hash ID (record_id). This ensures data integrity and prevents pipeline failures when the source API omits certain fields for specific reports.

​
Skills for agents

Download BTG Parceiros skills file

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