[sdk-generation-automation]

Changelog

2026-11-04

Breaking Change

Cosigners now pair with API users

Products: Cosigners

Scope: API + SDKs

• What's new
  Cosigner pairing now uses API users instead of API keys, with new endpoints to list, retrieve, pair, unpair, and update the callback handler of a cosigner's API users. The previous API key operations and the apiKeyId field are no longer part of the published API.

• Impact
  Integrations that pair cosigners with apiKeyId or the API key operations keep working for now, but those operations are no longer published and will be dropped from future SDK releases.

Affected endpoints:

1. Get all API users
2. Get API user
3. Pair API user
4. Unpair API user
5. Update API user callback handler
6. Get API user request status
7. Get all cosigners
8. Add cosigner

Add revoked and expirationTime key fields

Products: Key Link

Scope: API + SDKs

• What's new
  Validation key responses now always include a revoked flag and an expirationTime timestamp.

• Impact
  Strictly typed integrations that model validation key responses must account for the two new required fields.

Affected endpoints:

1. Get a validation key by keyId
2. Disables a validation key
3. Revokes a validation key
4. Add a new validation key
5. Get list of registered validation keys

Key Link and MPC key endpoints are now GA

Products: Keys

Scope: API + SDKs

• What's new
  The Key Link and MPC key management endpoints have graduated from beta to general availability.

• Impact
  These endpoints are now covered by general availability guarantees, and SDK users will find them under the stable namespaces instead of the beta ones.

Affected endpoints:

1. Get list of mpc keys
2. Get list of mpc keys by userId

Key Link and MPC key endpoints are now GA

Products: Key Link

Scope: API + SDKs

• What's new
  The Key Link and MPC key management endpoints have graduated from beta to general availability.

• Impact
  These endpoints are now covered by general availability guarantees, and SDK users will find them under the stable namespaces instead of the beta ones.

Affected endpoints:

1. Add a new signing key
2. Get list of signing keys
3. Register signing keys in bulk
4. Get bulk registration jobs
5. Get a bulk registration job
6. Get a signing key by keyId
7. Modify the signing keyId
8. >-

Set Tempo memo per transfer destination

Products: Tempo (Beta)

Scope: API + SDKs

• What's new
  The Tempo TIP-20 memo is now set on each transfer destination rather than on the transfer request itself, must be exactly 32 bytes when UTF-8 encoded, and is supported only for transfers with a single destination.

• Impact
  Existing Tempo transfers that set a memo at the request level will no longer include it on-chain until the value is supplied on the destination.

Affected endpoints:

1. Create a Tempo transfer transaction

Added

Add includeRevoked validation key filter

Products: Key Link

Scope: API + SDKs

• What's new
  Adds an optional includeRevoked query parameter so revoked validation keys can be included when listing keys, which are excluded by default.

• Impact
  Customers can now see revoked validation keys in list results when they opt in, and existing calls keep their current behavior.

Affected endpoints:

1. Add a new validation key
2. Get list of registered validation keys

Add validation key revocation

Products: Key Link

Scope: API + SDKs

• What's new
  Adds the ability to permanently revoke a validation key so it can no longer be used for validation.

• Impact
  Customers can permanently revoke validation keys through the API; this is a non-breaking addition and existing integrations continue to work.

Affected endpoints:

1. Revokes a validation key

Add new typed message transaction statuses

Products: Travel Rule

Scope: API + SDKs

• What's new
  Typed message transactions can now report the additional SIGNED and COMPLETED statuses, giving a more precise view of where a transaction stands in its lifecycle.

• Impact
  This is a non-breaking addition, but integrations that branch on transaction status should be prepared to receive these two new values.

Affected endpoints:

1. Create Trust Network Proof of Address
2. Retrieve Trust Network Proof of Address Signature

Changed

EA lifecycle state replaces beta

Products:

Scope: API + SDKs

• What's new
  Operations in Early Availability now report the lifecycle state ea instead of beta, in the Fireblocks-Lifecycle-State response header and the API spec. The SDK and CLI lifecycle warnings recognise ea and say the operation may change or break before it reaches GA; the SDKs' BETA_STATE constant (and Python's BETA_MESSAGE) is deprecated in favor of EA_STATE (EA_MESSAGE).

• Impact
  Code that reads the lifecycle state should expect ea instead of beta; earlier SDK and CLI versions only recognise beta and stop warning for EA operations until upgraded.

Affected endpoints:

Track missing-TRM manual decision status

Products: TRLink

Scope: API + SDKs

• What's new
  Manual missing-TRM decisions now report whether the decision was applied immediately or stored to be applied on a later processing attempt, and the current decision can be retrieved at any time.

• Impact
  Integrations reading manual decision results will see a new required status field and lowercase source values (manual, policy), which the API has always returned.

Affected endpoints:

1. Manual decision for missing TRM
2. Get manual decision for missing TRM

Cosigner endpoints are now generally available

Products: Cosigners

Scope: API + SDKs

• What's new
  The cosigner management endpoints have graduated from beta and are now generally available.

• Impact
  Existing integrations continue to work unchanged, now backed by a stable, non-beta interface.

Affected endpoints:

1. Get all cosigners
2. Add cosigner
3. Get cosigner
4. Rename cosigner
5. Get detailed cosigner version information

Deprecated

Deprecate disabling validation keys

Products: Key Link

Scope: API + SDKs

• What's new
  Disabling a validation key is deprecated and scheduled for sunset on 2027-01-01, with revocation as the replacement.

• Impact
  Integrations that disable validation keys keep working until the sunset date but will receive deprecation headers and should move to revocation.

Affected endpoints:

1. Get a validation key by keyId
2. Disables a validation key

---

[github-actions]

We've received your request. Thanks for your patience. (Note that this SDK code is auto generated)