Version May 28, 2026 - 5.121

mTLS certificate for outbound

AVAILABLE ON REQUEST

Background

Financial institutions require strong guarantees that systems interacting with their platforms are authentic and trusted. Standard authentication methods are sometimes not sufficient to prevent impersonation or unauthorized access.

Mutual TLS (mTLS) introduces an additional layer of security by enabling both parties in a connection to verify each other’s identity using digital certificates. This approach ensures that only trusted systems can exchange data, helping to protect sensitive financial information and reduce the risk of fraud.

Solution

Selligent now supports Mutual TLS (mTLS) to secure communication from Selligent to external systems.

This support is introduced across multiple components:

  • Web custom components
  • Plugins

 

What it looks like in the solution

mTLS is supported for outbound only, meaning from Selligent to external systems.

  • A dedicated certificate is created per customer.
  • mTLS is activated on request only (not enabled by default). Contact your Zeta representative.
  • If no certificate is configured, mTLS is considered not required.
  • Selligent is responsible for certificate management and maintenance.

 

API updates - Non-blocking data/load endpoint

Available to all customers

Background

Bulk data-processing endpoints (such as data loads and deletions) relied on a synchronous, blocking execution model. Under load, this led to scalability limitations, especially when processing large payloads or handling concurrent requests.

Solution

The data-processing pipeline has been fully redesigned to operate asynchronous end-to-end, removing blocking behavior and significantly improving scalability and stability.

Key improvements include:

  • Introduction of an async processing architecture (now generally available)
  • Addition of a per-list concurrency limiter to better control parallel execution
  • Support extended across key endpoints:
    • POST {list}/data/load
    • DELETE {list}/data
    • POST {list}/segments/{seg}/data/load
    • DELETE {list}/segments/{seg}/data

 

API updates - New endpoint for business key management

Available to all customers

Background

Defining and maintaining business keys for lists required manual handling and lacked a standardized API-driven approach.

Solution

A new endpoint enables centralized management of business keys for lists:

  • PUT /organizations/{organization}/lists/{api_name}/businesskey

Key capabilities:

  • Define or update a business key (1–3 fields)
  • Automatically creates a unique index if none exists (without overriding DBA-managed indexes)
  • Replaces any previously defined business key
  • Ensures consistent behavior with a 200 OK response on success

This simplifies data deduplication and improves data integrity management.

 

Documentation updates

Available to all customers

Alongside the documentation created for new features, several enhancements have been introduced to improve clarity and usability:

  • Improved Permission Visibility:

We’ve strengthened the link between features and their required permissions. It is now clearly indicated which permissions must be enabled to access and use a feature.

  • New CNIL Q&A Article:

A dedicated Q&A article has been added to support compliance with CNIL regulations in France, providing clear guidance and answers to common questions.

 

Corrections

  • Changes made to a page can again be saved as expected when the repeater ID contains encoded characters.
  • Two Factor Authentication via email was unexpectedly not working anymore. This has been resolved and emails can be sent again.
  • Alerts are now correctly logged when the cadence plan generates a status error.
  • When Content Block publishing is enabled and the email contains a Content block with multiple content components with the same ID, no email was sent out. This has now been resolved.
  • When content Block publishing is enabled and the Content Block contains an eventValue, once the Content Block is used in an email with scope Custom Event, the custom event scope should be referenced. This was not the case and has been resolved.
  • When using a template with a Boolean variable, refreshing the page and navigating away showed unexpectedly a dirty model popup. This has been resolved.
  • Validation messages in Responsive messages now correctly highlights the Content Blocks when clicked.
  • Lists can now be saved after sharing a list with a filter on same source field for different 1:1 scopes.
  • Preview of RCS cards now renders all elements correctly.
  • Line breaks in RCS messages are now rendered correctly in preview.