You can now create floating-rate banking bonds with a progressive rate (step-up CDBs), in which the percentage of CDI changes on predefined dates.

The Create Security endpoint accepts two new optional fields for FLOATING_RATE_BANKING_BOND securities:

• scaleType: INCREMENTAL (the new rate applies only from the change date onward) or RETROACTIVE (once the change date is reached, the new rate applies from the bond's start). The default is NONE.
• scaling: the list of rate changes, each with its date (date) and the new multiplier.

The multiplier field still indicates the rate in effect at issuance. Both fields must be sent together, and step-up rates are accepted only for bonds indexed to CDI, without spread and with interestPaymentPeriod equal to BULLET. The List Securities and Read Security by ID endpoints also return scaleType and scaling.

// REQUEST
// POST https://core.gorila.com.br/securities

{
  "type": "FLOATING_RATE_BANKING_BOND",
  "bankingBondType": "CDB",
  "initialDate": "2025-01-01",
  "maturityDate": "2030-01-01",
  "issuerId": "30306294000145",
  "issuanceFaceValue": 1000,
  "index": "CDI",
  "multiplier": 1.0,
  "scaleType": "INCREMENTAL",
  "scaling": [
    { "date": "2026-01-01", "multiplier": 1.05 },
    { "date": "2027-01-01", "multiplier": 1.10 }
  ]
}

Learn more in the "Step-up CDB" section of Security.

You can now set the classification of a custom security when creating it, with the new optional classificationId field.

In the Create Security endpoint, with the CUSTOM type, send in classificationId the identifier of the desired classification, which you can get from List Securities Classifications. Without the field, the security is classified based on its asset class (assetClass).

//REQUEST
//POST https://core.gorila.com.br/securities

{
  "type": "CUSTOM",
  "name": "Fazenda Boa Vista",
  "description": "Fazenda Boa Vista - MG",
  "assetClass": "TANGIBLE",
  "initialDate": "2022-04-04",
  "classificationId": "TANGIBLE_GENERIC"
}

Learn more in Custom Security.

The Net Asset Value (NAV), market value and TWR of portfolios and economic groups can now be calculated from the exposure perspective. This avoids distorted returns in portfolios leveraged with futures and forwards.

The new optional marketValueType parameter accepts two values:

• AUTO (default): keeps the previous behavior. NAV and market value follow the wealth perspective, in which futures and forwards have a zero market value.
• EXPOSURE: futures and forwards are always calculated from the exposure perspective (quantity × closing price × contract multiplier). In NAV and market value, they contribute the full value of the contracts (signed), and TWR is measured over the exposure.

The parameter is available in:

• Read Net Asset Value and Read Economic Group Net Asset Value
• List Position Market Values and List Economic Group Positions Market Values
• Read Time-Weighted Return and Read Economic Group Time-Weighted Return
• List Position Time-Weighted Returns and List Economic Group Positions Time-Weighted Returns

Learn more in Exposure.

Portfolios now support crypto futures contracts, including Bitcoin (BIT), Ethereum (ETR) and Solana (SOL) futures.

These contracts can be registered in portfolio transactions and are included in the portfolio's metrics, like the other futures contracts. See how to register a futures transaction in Transactions - Examples.

Owners and admins of business organizations can now list, create and delete the organization's API keys directly in GorilaVIEW, without contacting Gorila's support team. Organization API keys are now called OATs.

On the organization management page in GorilaVIEW, available to users with the Owner or Admin role, you can:

• list, create and delete the organization's API keys (OATs);
• define whether the organization's users can create Personal Access Tokens (PATs).

The new name is only a change in terminology: existing keys keep working and are sent the same way, in the Authorization header. PATs remain the personal keys, tied to a user.

Keys issued by Gorila's team are now delivered through a single-use link, so that Gorila employees do not have access to your key.

Learn more about API keys in Organization.

Agribusiness credit rights certificates (CDCA, Certificados de Direitos Creditórios do Agronegócio) are now supported, with the CORPORATE_BONDS_CDCA security type. They are handled like debêntures, CRIs and CRAs, with integrated prices and events.

As with the other corporate bonds, you don't need to create the security: find it with List Securities and register transactions with Create Transaction, identifying the CDCA by securityId or ISIN.

Learn more in Transactions - Examples.

Organizations now have more control over their users' Personal Access Tokens (PATs): requests made with the PAT of a deactivated user, or of an organization that has disabled PATs, are rejected.

The API now checks two conditions on every request authenticated with a PAT:

• Active user: if the user who owns the PAT has been deactivated in Gorila, the request returns 401 with the message inactive user.
• PATs enabled in the organization: organizations can disable the use of PATs by their users. While PATs are disabled, new PATs cannot be created, and requests with the organization's existing PATs return 401:

{
  "code": 401,
  "message": "Personal Access Tokens are disabled for this organization"
}

The organization's API keys are not affected by these checks.

GorilaCORE now supports Gorila's new security classification: a hierarchical tree of classes and subclasses with up to 4 levels, which you can use to filter and group the metrics of portfolios and economic groups.

In the tree, an inflation-indexed government bond, for example, is under "Fixed Income > Inflation Indexed > Government Bond". The levels go from CLASSIFICATION_L0 (the broadest) to CLASSIFICATION_L3 (the most detailed). What's new:

• Classification tree: the new List Securities Classifications endpoint lists the classifications, with filters by level (classificationLevel) and by parent classification (parentId).
• Classification of each security: security objects, such as those returned by List Securities and Read Security by ID, now include the classifications field, with the security's classification at each level.
• Filter: most metrics endpoints of portfolios and economic groups accept the securityClassification filter, with the identifier of a classification.
• Grouping: the per-position endpoints that accept groupBy, such as List Position Market Values, accept grouping the result by classification level: CLASSIFICATION_L0, CLASSIFICATION_L1, CLASSIFICATION_L2 or CLASSIFICATION_L3.

Learn more in Security Classification.

The portfolio object now has two new fields: alias, a nickname defined by your organization, and connected, which indicates whether the portfolio belongs to someone else and was shared with your organization.

Both fields are returned by endpoints such as List Portfolios and Read Portfolio by ID:

• connected: true when the portfolio was shared with (connected to) your organization and is not owned by it.
• alias: the nickname your organization gives the portfolio, or null when there is none. The original name (name) does not change, and the portfolio's owner does not see the alias.

The alias is useful, for example, to identify connected portfolios with your organization's internal codes. To set, change or remove it, use Update Portfolio by ID, sending alias with the new value or null:

{
  "alias": "ID-0042"
}

Learn more in Portfolio.

Banking bonds can now be created with the new LCD type, to represent Letras de Crédito do Desenvolvimento.

In the Create Security endpoint, send bankingBondType equal to LCD when creating a fixed-rate (FIXED_RATE_BANKING_BOND) or floating-rate (FLOATING_RATE_BANKING_BOND) banking bond. The resulting security has the CORPORATE_BONDS_LCD type and, like the other banking bonds, can then be used in transactions through the returned securityId.

Learn more in Security.

You can now query the dividend yield of a portfolio's positions: how much each security paid out in income, per unit, relative to its price over a period.

The new List Position Dividend Yield endpoint returns, for each security in the portfolio:

• dividendYield: the dividend yield for the period, in decimal format (0.05 = 5%);
• hasOpenPositionAllDays: whether there was a position on every day of the period;
• currency: the security's payment currency;
• security: the security's basic data.

The dividend yield is the sum of the income per unit with ex-dates in the period, divided by the security's closing price. The period is defined by startDate and endDate; when endDate is not informed, today's date is used. The endpoint also allows filtering by security, asset class, security type and broker.

Learn more in Dividend Yield.

Searching for securities by symbol is now more precise: the search only returns securities whose symbol is exactly the searched term or starts with it.

The change affects the search parameter of the List Securities endpoint. Previously, symbol matching was approximate, which could return incorrect results, for example, when searching by CNPJ. Searches by the security's descriptive name are not affected and remain approximate.

Learn more in Security.

The transaction lists of portfolios and economic groups now accept new filters, so you can fetch only the transactions you need instead of filtering the full list on your side.

The List Transactions and List Economic Group Transactions endpoints accept the following optional query parameters:

• brokerId: the broker's CNPJ.
• securityId: Gorila's identifier of the security.
• type: the transaction type, such as REGULAR or CUSTODY_TRANSFER.
• side: the transaction direction, BUY (purchase) or SELL (sale).

The filters can be combined with each other and with the period filters (startDate and endDate). For example, to list only the sales of a security:

GET /portfolios/{portfolioId}/transactions?securityId=1651&side=SELL

Learn more in Transaction.

Managed funds can now be created as securities in GorilaCORE, with the new MANAGED_FUND type, and receive transactions in portfolios.

In the Create Security endpoint, send type equal to MANAGED_FUND. Registration follows the same model as investment clubs (INVESTMENT_CLUB): name (name), description (description), asset class (assetClass) and initial date (initialDate) are required, and the cnpj is optional.

As with investment clubs, the quota value is provided by your organization. Use Upsert Security Prices to send the price series, List Security Prices to query it and Delete Security Prices to remove the price of a date.

Learn more in Security.

You can now query the invested amount of economic groups, both consolidated and per position, with the same views already available for portfolios.

Two new endpoints were added:

• Read Economic Group Invested Amount: time series of the economic group's invested amount, with a choice of frequency (frequency).
• List Economic Group Positions Invested Amount: invested amount of each position of the economic group, with the option to group the result (groupBy).

The group's invested amount is the sum of the invested amounts of the positions of its portfolios. Both endpoints accept the same filters as the portfolio version (security, asset class, security type and broker), and values are expressed in Brazilian reais (BRL).

Learn more in Invested Amount.

GorilaCORE now supports economic groups: named groupings of up to 10 portfolios that you can analyze together, as if they were a single consolidated portfolio.

An economic group is defined by a name (name) and by the list of IDs of the portfolios that compose it (portfolios). Each group returns a status (PROCESSING, COMPLETED or INVALID), which is COMPLETED only when all of its portfolios have been processed. The new endpoints are:

• Management: Create Economic Group, List Economic Groups (with search by name), Read Economic Group by ID, Update Economic Group by ID and Delete Economic Group by ID.
• Group metrics: Read Economic Group Net Asset Value, Read Economic Group Profit & Losses and Read Economic Group Time-Weighted Return.
• Positions: List Economic Group Positions, List Economic Group Positions Average Prices, List Economic Group Positions Internal Rate of Return, List Economic Group Positions Market Values, List Economic Group Positions Profit & Losses, List Economic Group Positions Time-Weighted Returns and List Economic Group Positions Security Prices.
• Transactions and events: List Economic Group Transactions and List Economic Group Security Events, with the transactions and security events of the group's portfolios.

These views follow the same concepts and parameters as the equivalent portfolio endpoints.

Learn more in Economic Group.

Four new banking bond types can now be created: RDB, RDC, DPGE and repurchase agreements (operações compromissadas).

In the Create Security endpoint, the bankingBondType field now accepts the values below, both for fixed-rate (FIXED_RATE_BANKING_BOND) and floating-rate (FLOATING_RATE_BANKING_BOND) bonds. Creation follows the same flow as CDBs:

Learn more in Security.

Banking bonds can now be registered with periodic interest (coupon) payments, through two new optional fields when creating the security.

When creating fixed-rate (FIXED_RATE_BANKING_BOND) or floating-rate (FLOATING_RATE_BANKING_BOND) banking bonds with Create Security, you can now provide:

• interestPaymentPeriod: interest payment frequency. Accepted values: BULLET (default, no intermediate payments), MONTHLY, EVERY_2_MONTHS, EVERY_3_MONTHS, EVERY_4_MONTHS, EVERY_6_MONTHS or YEARLY.
• issuanceFaceValue: face value at issuance.

Both fields are also returned by List Securities and Read Security by ID.

Example of a fixed-rate CDB with semiannual interest payments:

// REQUEST
// POST https://core.gorila.com.br/securities

{
  "type": "FIXED_RATE_BANKING_BOND",
  "bankingBondType": "CDB",
  "initialDate": "2024-12-02",
  "maturityDate": "2027-12-02",
  "issuerId": "03215790000110",
  "issuanceFaceValue": 1000,
  "interestPaymentPeriod": "EVERY_6_MONTHS",
  "yield": 0.12
}

Learn more in Security.

Two new endpoints return the invested amount of portfolios and positions: the acquisition cost of the units the investor still holds, which does not follow price fluctuations.

• Read Invested Amount: time series of a portfolio's invested amount, with a choice of frequency (frequency).
• List Position Invested Amount: invested amount of each position of a portfolio, with the option to group the result (groupBy).

Compared with the market value, the invested amount shows a position's unrealized gain or loss. Compared with the Net Asset Value (NAV), it puts the portfolio's value side by side with the acquisition cost of the units it holds.

Learn more in Invested Amount.

Three new banking bond types can now be created: LIG (Letra Imobiliária Garantida) and the subordinated Letras Financeiras LFS and LFSN.

In the Create Security endpoint, the bankingBondType field now accepts the values below, both for fixed-rate (FIXED_RATE_BANKING_BOND) and floating-rate (FLOATING_RATE_BANKING_BOND) bonds:

As with the other banking bonds, use the returned securityId to create transactions with the new security.

Learn more in Security.