Skip to main content
Superlógica Assinaturas is a subscription management platform that helps businesses manage their recurring revenue, customer subscriptions, and billing processes. It provides tools for managing clients, subscriptions, and recurring payments.

​
Configuring Superlógica Assinaturas as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Superlógica Assinaturas 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 the following credentials to connect to Superlógica Assinaturas:
  • App Token: The app token from Superlógica.
  • Access Token: The access token from Superlógica.
  • Start Date: The earliest date from which records will be synced (e.g., YYYY-MM-DD). Used for data extractions like the aggregated MRR stream.
If you don’t know how to generate the tokens, please check this documentation.
The tokens are valid for 1 year, after that to continue using the APIs a new one must be generated.
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 all streams or pick specific ones that matter most to you.
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 data - which is good if, for example, you want to keep every record ever fetched.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.
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. 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 Superlógica Assinaturas and their corresponding fields:
Stream for managing client information. It fetches all clients, including active, inactive, and frozen records.Fields:
Stream for managing subscription and recurring payment information.Fields:
Lean aggregated stream providing MRR/total metrics per active and deactivated contract-plan. It hits the same endpoint as assinaturas but uses an aggregated view. Join keys and aggregated metrics are kept - join back to assinaturas/clientes for client/contract/plan details.
Stream for retrieving charge and receivable information.Fields:
Stream for retrieving only the active (non-trial) Superlógica contracts.This stream generates an “as of today” snapshot. It is deliberately un-deduplicated (contains no primary keys) to match the external system’s exact record counts and preserve pagination artifacts.Fields:
Stream for retrieving deactivated Superlógica contracts. Contains the same fields as the Contratos Ativos stream.
Stream for retrieving pending Superlógica contracts. Contains the same fields as the Contratos Ativos stream.
Stream for retrieving trial Superlógica contracts. Contains the same fields as the Contratos Ativos stream.
Stream for managing expense movements. Hits /financeiro/caixa filtered to the expense side.
Stream from the Superlógica Assinaturas API that retrieves invoices and their corresponding line items.
The list fields above are emitted as JSON-encoded strings to prevent upstream schema changes from impacting downstream table schemas and to ensure compatibility with data warehouse environments (e.g., BigQuery).
Stream for managing subscription plans.
Stream for managing products and services.
Stream for managing eventual (one-off) revenues.

​
Data Model

The following diagram illustrates the relationships between the core data streams in Superlógica Assinaturas. The arrows indicate the join keys that link the different entities.

​
Implementation Notes

​
Despesas Stream Behavior

For the Despesas stream, virtual/projected movements (fl_virtual_mov="1") do not naturally contain an id_movimentacao_mov field in the API response. To avoid dropping this data, the connector synthesizes the primary key for these records using the id_contabanco_mov or id_origemvirtual_mov field.

​
Data Sync Behavior

  • Nota Fiscal API Window: Without explicitly provided start and end dates (dtInicio/dtFim), the Superlógica Assinaturas API silently applies a restrictive default date window when fetching the Nota Fiscal stream. To prevent massive data gaps, the connector automatically applies wide range filters under the hood to guarantee that all invoice records are thoroughly fetched.
  • Nested Schema Flattening: The servicos field in the Nota Fiscal stream is emitted as a JSON-encoded string instead of an array of objects. This ensures that any sub-field changes made on the Superlógica side do not trigger downstream schema evolutions or failures in your Lakehouse. Ensure you use JSON extraction functions in your queries if you wish to analyze the underlying fields.

​
Deduplication and Sync Behavior

  • Contratos Ativos: This stream intentionally does not declare any primary keys. By avoiding deduplication, the table reflects the exact raw row output from the source (including any identical records arising from the source’s pagination artifacts), ensuring the total row count precisely matches what the external system reports for active, non-trial contracts “as of today”. When syncing this stream, it is recommended to use the Full table sync type so the entire target table is replaced in each run, preserving the source’s original counts.

​
API Limits & Behavior

  • Page Size Limits: Superlógica’s maximum allowed page size is 200 items. Requests exceeding this limit will be rejected by the API. The connector strictly adheres to this to avoid extraction failures.
  • Data Completeness & Windowing: Several Superlógica endpoints (like contracts) silently default to “as of today” snapshots if specific date filters are not provided. Attempting to pass extremely large date ranges results in API timeouts. To prevent massive data undercounting, the connector implements specialized year-by-year windowed pagination (starting from 2015) to guarantee the safe and complete extraction of your account’s entire history.
  • Charges History: The cobrancas endpoint utilizes an internal bypass parameter (semFiltroPorData=true) to override restrictive API defaults, ensuring all historical records are retrieved.
  • Transient Routing Errors: Superlógica’s API gateway may occasionally return an HTTP 404 error with the body message Could not route request. This represents a known backend routing hiccup, not a missing endpoint. The connector automatically treats this specific error as a transient issue and safely retries the request, preventing momentary network blips from aborting an otherwise successful extraction (such as during large syncs).
  • Disjoint Datasets: Some financial streams, such as receitas_eventuais (composition/one-off revenues), split data into mutually exclusive sets. The connector automatically cycles through these disjoint structures to form a single cohesive table for you.