Skip to content

v32.0.0

Choose a tag to compare

View all tags
@sdk-generation-automation sdk-generation-automation released this 23 Sep 10:30
· 0 commits to 99eb70b0aeef30192cd7fa2e2cdf8ebc1924684d since this release
v32.0.0
695c518

Changelog

2026-09-23

SDK and CLI updates: TypeScript SDK v32.0.0 • Python SDK v32.0.0 • Java SDK v32.0.0 • CLI v12.0.0

Breaking Change

Move the mTLS CSR endpoint under webhook settings and add ECDSA support

Products: Webhooks V2

Scope: API + SDKs

  • What's new
    The mTLS CSR endpoint moves from GET /webhooks/mtls/csr to GET /webhooks_settings/mtls_csr, alongside the other webhook settings resources. It also accepts an optional keyAlgorithm query parameter, RSA or ECDSA, and echoes the algorithm the CSR was issued for back on the response.

  • Impact
    Customers can request ECDSA-based CSRs for smaller, faster certificate issuance. Callers of the previous path must move to the new one.

Affected endpoints:

  1. Get mTLS CSR

Added

Add transfer status to internal transfers

Products: Exchange accounts

Scope: API + SDKs

  • What's new
    Internal transfer responses now include an optional status field and a systemMessages array describing the health of the transfer, populated when the transfer is processed through the transaction manager flow.

  • Impact
    Customers can see the outcome and any system messages for an internal transfer directly in the response; existing integrations continue to work since both fields are optional.

Affected endpoints:

  1. Internal transfer for exchange accounts

Add Compliance Orchestrator API (private beta)

Products: Compliance Orchestrator

Scope: API + SDKs

  • What's new
    Adds new Compliance Orchestrator endpoints for triggering on-demand compliance screenings, retrieving screening results, and managing workflow configurations.

  • Impact
    Customers enrolled in the private beta can programmatically screen addresses and transactions before they exist on-chain.

Affected endpoints:

  1. Trigger a Compliance Orchestrator screening
  2. Get a Compliance Orchestrator screening's result
  3. Get a Compliance Orchestrator workflow
  4. Update a Compliance Orchestrator workflow's status

Add approval request approve endpoint (beta)

Products: Approvals (Beta)

Scope: API + SDKs

  • What's new
    Adds a beta endpoint to approve a pending approval request by signing the request's signable data with a registered approval API key.

  • Impact
    Customers can programmatically approve approval requests through the API instead of using the Console.

Affected endpoints:

  1. Approve an approval request

Add approval key management endpoints (beta)

Products: Approvals (Beta)

Scope: API + SDKs

  • What's new
    Adds beta endpoints to register, list, and delete approval public keys for API users, enabling cryptographic signing of approval requests.

  • Impact
    Customers can manage approval signing keys for API users through the API.

Affected endpoints:

  1. Register an approval key
  2. List approval keys
  3. Delete an approval key

Add Compliance Orchestrator screening endpoints (beta)

Products: Compliance Orchestrator

Scope: API + SDKs

  • What's new
    Adds private beta endpoints to trigger on-demand compliance screenings against active workflows and retrieve screening results with audit logs.

  • Impact
    Customers can programmatically run compliance screenings before transactions exist on-chain.

Affected endpoints:

  1. Trigger a Compliance Orchestrator screening
  2. Get a Compliance Orchestrator screening's result

Changed

Token request authorization header rules

Products: Webhooks V2

Scope: API + SDKs

  • What's new
    An authorization header can be set on the token request to your authorization server when credentials are sent in the request body, and is rejected when they are sent in that header instead.

  • Impact
    Customers whose token endpoint sits behind a gateway can supply their own authorization header, while conflicting combinations are rejected up front.

Affected endpoints:

  1. Create OAuth credentials
  2. Update OAuth credentials

Custom header limit counted per name

Products: Webhooks V2

Scope: API + SDKs

  • What's new
    The ten-header limit on webhook custom headers is counted per header name rather than per delivered header line, and OAuth bearer tokens are cached until they expire instead of being fetched for every delivery.

  • Impact
    Customers can attach multi-value headers without consuming the limit, and authorization servers receive far fewer token requests.

Affected endpoints:

  1. Create OAuth credentials
  2. Get all OAuth credentials
  3. Update OAuth credentials

Authorization header and OAuth are exclusive

Products: Webhooks V2

Scope: API + SDKs

  • What's new
    A webhook can use either OAuth credentials or its own authorization custom header, but not both, and the header now accepts only a single string value.

  • Impact
    Customers should configure a webhook with either OAuth credentials or an authorization header; combining the two is not supported.

Affected endpoints:

  1. Create a new webhook
  2. Update webhook

Clear OAuth credential maps with a null value

Products: Webhooks V2

Scope: API + SDKs

  • What's new
    The custom claims, body parameters and headers on stored OAuth credentials can now be emptied in one step by setting the whole field to null, in addition to deleting individual keys.

  • Impact
    Customers can clear an entire map without listing every key, and requests that previously failed with a validation error now succeed.

Affected endpoints:

  1. Update OAuth credentials

Fixed

Clarify contract parameter value types

Products: Contract Interactions, Contract Templates, Deployed Contracts, Tokenization

Scope: API + SDKs

  • What's new
    The documentation for a contract parameter's value now explains that its shape follows the ABI type: strings for text and addresses, numbers for integers, booleans, arrays, and nested entries for tuples.

  • Impact
    Customers get accurate guidance on how to supply non-string parameter values when interacting with contracts.

Affected endpoints:

  1. Deploy contract
  2. Get deterministic address for contract deployment
  3. Call a read function on a deployed contract
  4. Call a write function on a deployed contract
  5. Issue a token on one or more blockchains
  6. Issue a new token
  7. Decode a function call data, error, or event log
  8. Return deployed contract data
  9. Return deployed contract data by id

Correct gas value types on transaction receipts

Products: Contract Interactions

Scope: API + SDKs

  • What's new
    Gas amount and price values in transaction receipt responses are now typed as 64-bit integers, so large chain values are represented accurately.

  • Impact
    Gas values that exceed the 32-bit range are no longer at risk of being truncated or misparsed by SDK clients.

Affected endpoints:

  1. Get transaction receipt
Assets 2
Loading