> For the complete documentation index, see [llms.txt](https://docs.caf.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caf.io/caf-api/connect/available-resources/joint-resolution-6/changelog.md).
# Changelog
## 2026-07-01 - RS6 GMUD CNPJ Alphanumeric
Changes in data dictionary fields, in compliance with **RS6 GMUD CNPJ Alphanumeric**.
The addition/alteration of these fields does **not impact existing** fraud records and is **not retroactive**. Therefore, existing records continue to be validated against the **pre-existing schema**.
During a transition period, new fraud entries can be created using the `informacoes_bancarias_destino.codigo_instituicao` field. After **to be defined**, only fraud entries using the `informacoes_bancarias_destino.ispb` field will be accepted.
| **Field** | **Type of Change** | **Description** |
| ----------------------------------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `informacoes_bancarias_destino.ispb` | Inclusion | Deprecates the `codigo_instituicao` field. ISPB in string format. Conditional field**¹**. |
| `informacoes_bancarias_destino.codigo_instituicao` | Deprecated | Change the field requirement rule.
Previous: Required field;
Current: Conditional field¹.
|
| `instituicao_responsavel.cnpj_origem` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacao_reclamante.documento.numero` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacao_executor.documento.numero` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacao_reclamante.documento_representante_legal[N].numero` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacao_executor.documento_representante_legal[N].numero` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacoes_bancarias_destino.conta.documento_representante_legal[N].numero` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacoes_bancarias_destino.conta.titular.documento.numero` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
| `informacoes_bancarias_destino.chave_pix.valor` | Alteration | Change the field format rule.
Previous: Numeric string;
Current: Alphanumeric string².
|
> **¹**: This field is **required**, `informacoes_bancarias_destino.codigo_instituicao` or `informacoes_bancarias_destino.ispb`, only one of the two must be provided.
> **²**: New validation format applies only to the CNPJ type.
## 2026-03-01 - New Endpoints (OAuth2)
Introduces critical changes to the API endpoints and authentication mechanisms to enforce stricter security standards. The authentication architecture is transitioning to an **OAuth2-based model**. Concurrently, the workflow for clients requiring **Mutual TLS (mTLS)** configurations has been restructured. To accommodate these infrastructure updates, the base API domains and endpoints have been migrated.
All active integrations must be updated to utilize the new endpoints specified below:
| **Environment** | **Old Endpoint** | **New Endpoint** |
| --------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------- |
| Sandbox | [api.stg.combateafraude.com.br/fraud](https://api.stg.combateafraude.com.br/fraud) | [api.us.stg.caf.io/v1/rs6](https://api.us.stg.caf.io/v1/rs6) |
| Sandbox **(mTLS)** | [mtls.stg.combateafraude.com.br/fraud](https://mtls.stg.combateafraude.com.br/fraud) | [mtls.us.stg.caf.io/v1/rs6](https://mtls.us.stg.caf.io/v1/rs6) |
| Production | [api.prd.combateafraude.com/fraud](https://api.prd.combateafraude.com/fraud) | [api.us.prd.caf.io/v1/rs6](https://api.us.prd.caf.io/v1/rs6) |
| Production **(mTLS)** | [mtls.prd.combateafraude.com/fraud](https://mtls.prd.combateafraude.com/fraud) | [mtls.us.prd.caf.io/v1/rs6](https://mtls.us.prd.caf.io/v1/rs6) |
Detailed technical instructions regarding the new OAuth2 authentication flow and mTLS configuration have been migrated to dedicated documentation pages. Please consult the following resources to proceed with the integration updates:
* [OAuth2 Authentication Guide](/caf-api/connect/authentication/authenticating.md);
* [Using mTLS Guide](/caf-api/connect/authentication/using-mtls.md);
* [Available Resources](/caf-api/connect/available-resources/joint-resolution-6.md).
## 2025-05-14 - Paginated Fraud Query Responses
Adopts the approach of paginating responses, when deal with a large number of fraud entries in the response. Changes in the [Suspected fraud query](/caf-api/connect/available-resources/joint-resolution-6/suspected-fraud-query.md).
Changes in the request schema body:
| **Field** | **Type of Change** | **Description** |
| --------- | ------------------ | -------------------------------------------------------------------------------------- |
| `page` | Inclusion | It's a optional field, indicates the page number to be request when a paginated query. |
Changes in the response schema:
| **Property** | **Type of Change** | **Description** |
| ------------- | ------------------ | ------------------------------------------------------------ |
| `totalPages` | Inclusion | In a paginated response, indicates de total number of pages. |
| `currentPage` | Inclusion | In a paginated response, indicates de current page number. |
## 2025-04-16 - Adjust RS6 Fraud Creation Response
Inclusion of fraud token in response of successful fraud creation.
| **Property** | **Type of Change** | **Description** |
| ------------- | ------------------ | ---------------------------------------------------------------------------------- |
| `fraudToken` | Inclusion | Provides the fraud token from a **single** creation. It\*\*s a string property. |
| `fraudTokens` | Inclusion | Provides the fraud tokens from a **batch** creation. It's a string array property. |
For more information please check the [Suspected fraud creation page](/caf-api/connect/available-resources/joint-resolution-6/suspected-fraud-creation.md).
## 2025-03-10 - RS6 GMUD Q1/25
Changes in data dictionary fields, in compliance with **RS6 GMUD Q1/25**.
The addition/alteration of these fields does **not impact existing** fraud records and is **not retroactive**. Therefore, existing records continue to be validated against the **pre-existing schema**.
| **Field** | **Type of Change** | **Description** |
| --------------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| informacoes\_bancarias\_destino
.chave\_pix
| Inclusion | - |
| informacoes\_bancarias\_destino
.linha\_digitavel\_boleto
| Inclusion | - |
| `registro.modalidade_fraude` | Inclusion | - |
| `registro.motivo` | Alteration | Change the field requirement rule.
Previous: Optional field;
Current: Conditional field¹.
|
| informacoes\_bancarias\_destino
.agencia
| Alteration | Change the field requirement rule.
Previous: Optional field;
Current: Conditional field².
|
Are changed in the default schema, used in the [Suspected fraud creation](https://github.com/combateafraude/public-docs/blob/docs-api/connect-api/available-resources/joint-resolution-6/available-resources/suspected-fraud-creation.md) and in the [Suspected fraud query](https://github.com/combateafraude/public-docs/blob/docs-api/connect-api/available-resources/joint-resolution-6/available-resources/suspected-fraud-query.md).
This addition **impact existing** fraud records and is **retroactive**. The inclusion of **data\_ultima\_alteracao** only affects the [Suspected fraud query](https://github.com/combateafraude/public-docs/blob/docs-api/connect-api/available-resources/joint-resolution-6/available-resources/suspected-fraud-query.md).
| **Field** | **Type of Change** | **Description** |
| ----------------------- | ------------------ | ------------------------------------------------------------ |
| `data_ultima_alteracao` | Inclusion | Indicates the last change of the record in Interoperability. |
> **¹**: This field is **required** when `registro.modalidade_fraude` is equal to: 98 or 99. Field with minLength of 20 chars requirement.
> **²**: This field is **required** when `informacoes_bancarias_destino.chave_pix.tipo` is equal to: 6.
## 2025-02-11 - Adjust RS6 Fields Requirement
Changes in data dictionary fields requirement, given understanding of RS6 Interoperability Committee.
The alteration of these fields **impact existing** fraud records and is **retroactive**.
| **Field** | **Type of Change** | **Description** |
| ---------------------------------------------------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| informacoes\_bancarias\_destino
.agencia
| Alteration | Change the field requirement rule.
Previous: Required field;
Current: Optional field.
|
| informacoes\_bancarias\_destino
.codigo\_instituicao
| Alteration | Change the field requirement rule.
Previous: Conditional field¹;
Current: Required field.
|
| informacoes\_bancarias\_destino
.conta
| Alteration | Change the field requirement rule.
Previous: Optional field;
Current: Conditional field¹.
|
| informacoes\_bancarias\_destino
.conta.tipo
| Alteration | Change the field requirement rule.
Previous: Conditional field¹;
Current: Required field.
|
| informacoes\_bancarias\_destino
.conta.numero
| Alteration | Change the field requirement rule.
Previous: Optional field;
Current: Required field.
|
Are changed in the `SuspectedFraudOccurence` schema, used in the [Suspected fraud creation](/caf-api/connect/available-resources/joint-resolution-6/suspected-fraud-creation.md) and in the [Suspected fraud query](/caf-api/connect/available-resources/joint-resolution-6/suspected-fraud-query.md).
> **¹**: This field is **required** when `registro.atividade_relacionada` is equal to: 4, 5, 6, 7 or 8.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.caf.io/caf-api/connect/available-resources/joint-resolution-6/changelog.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.