> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction/changelog.md).

# Changelog

All notable changes to the Phalcon Compliance API are documented here. Entries are listed in reverse chronological order.

## 2026-07-16

Introduces the `riskProfile` field as the single source of risk data, replacing several legacy fields.

### Added

| Field / Schema                                                                                                        | Applies To                                       | Description                                                                                           |
| --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------ | ----------------------------------------------------------------------------------------------------- |
| `riskProfile`                                                                                                         | `AddressScreenResult`, `TransactionScreenResult` | Structured risk summary with `entityRisks`, `interactionRisks`, and `behaviorRisks`. Always returned. |
| `taskId`                                                                                                              | Sync screening responses                         | Both address and transaction synchronous responses now return `taskId`.                               |
| `note`                                                                                                                | `AddressScreenResult`, `TransactionScreenResult` | User-defined note for the address or transaction.                                                     |
| `RiskProfile`, `EntityRisk`, `InteractionRisk`, `ExposurePart`, `ExposureTotal`, `BehaviorRisk`, `BehaviorRiskFields` | New schemas                                      | Supporting schemas for the `riskProfile` structure.                                                   |

### Deprecated

{% hint style="warning" %}
The following fields are scheduled for removal on **2026-08-31**. Please migrate to `riskProfile` before this date.
{% endhint %}

| Field                                                                          | Applies To                | Migration                                                          |
| ------------------------------------------------------------------------------ | ------------------------- | ------------------------------------------------------------------ |
| `includeDetails`                                                               | Request parameter         | No longer needed — `riskProfile` is always returned.               |
| `alerts[].riskDetail`                                                          | Response                  | Use `riskProfile` instead.                                         |
| `isBlacklisted`, `blacklistedInfo`, `isWhitelisted`, `whitelistedInfo`         | `AddressScreenResult`     | Use `riskProfile.entityRisks` with type `blacklist` / `whitelist`. |
| `fromIsBlacklisted`, `toIsBlacklisted`, `fromIsWhitelisted`, `toIsWhitelisted` | `TransactionScreenResult` | Use `riskProfile.entityRisks`.                                     |

### Removed

| Field               | Description                                         |
| ------------------- | --------------------------------------------------- |
| `enableReScreening` | Request parameter fully removed from documentation. |

***

## 2026-04-29

Deprecates the address re-screening parameter and removes related status fields.

### Deprecated

| Field               | Applies To                        | Description                                            |
| ------------------- | --------------------------------- | ------------------------------------------------------ |
| `enableReScreening` | `AddressScreen` request parameter | Accepted for backward compatibility but has no effect. |

### Removed

| Field               | Description                                   |
| ------------------- | --------------------------------------------- |
| `reScreeningStatus` | Removed from `AddressScreenResult` responses. |

***

## 2026-03-30

Adds support for multi-input BTC transactions.

### Added

| Field           | Applies To            | Description                                                                                      |
| --------------- | --------------------- | ------------------------------------------------------------------------------------------------ |
| `fromAddresses` | `TransactionTransfer` | List of source addresses for BTC transactions where a transfer can be funded by multiple inputs. |

### Changed

| Field                             | Description                                                                                        |
| --------------------------------- | -------------------------------------------------------------------------------------------------- |
| `TransactionScreen.transferIndex` | Can be used alone or together with `toAddress`. For BTC transactions, represents `toAddressIndex`. |