Highlights

APIM 3.0

• The Git Integration supports Service Subscriptions

AgentCreator

• Pipeline tags enable you to label pipelines as Agent and Tools

New User Experience

• Waffle menu, Designer, and Project Manager

Snaps

• Added the HTML to PDF Converter Snap to the PDF Snap Pack

Platform: Patch Updates

Snaps: Patch Update

User Experience Updates

Updates to the look and feel of the waffle menu and Designer bring consistency to your experience in the SnapLogic interface. To better align functionality with your workflow, Classic Manager features have been split between the new Project Manager and the existing Admin Manager and Monitor. Refer to the following video and Project Manager FAQs for more information.

Waffle Menu

The waffle menu now provides one-click access to Development apps, Mission Control, Resources, and Help & Policies:

Open

Development apps

Designer now shares the look and feel of Monitor and Admin Manager, with a matching header and a redesigned toolbar:

Open

In environments with both Classic APIM and APIM 3.0 enabled, the API Management option opens the interface for both:

Open

Mission Control

Admin Manager now contains the majority of the settings that were available in Classic Manager. Refer to Administrative settings for a mapping of the old settings to their new location.

• The Monitor Notification Center contains the alerts, activity logs, and the configuration for notifications that were available in Classic Manager. Refer to Administrative settings for a mapping of the old settings to their new location.

• The new Project Manager provides functionality to manage projects, generate statistics, view calendars for scheduled tasks, and search for assets.

Classic Manager

To better support your workflow, Classic Manager functionality has been split between the new Project Manager, Admin Manager, and Monitor. Until the Classic Manager is retired in the August 2026 release, you can access it from the waffle menu:

Open

For more information

Watch this short video and refer to the Project Manager FAQs:

Open

API Management 3.0

Enhancements

The migration tool supports migration of Applications and Subscriptions. Subscribers can continue using their existing API keys. Learn more.

• The Git Integration (for GitHub only) supports tracking of Applications and Subscriptions. Learn more.

• When you migrate an API Version or Proxy with subscribers from Classic APIM and publish it to the APIM 3.0 Developer Portal, the subscribers receive an email notification.

• When an API version or Proxy is migrated from Classic APIM and published on the APIM 3.0 Developer Portal, all subscribers receive an email notification.

• When APIM 3.0 is enabled in an environment, the Developer Portal builds automatically. An admin no longer has to make a configuration change to trigger the build.

Fixed Issues

• When a new Developer Portal user receives a welcome email with a default password, login no longer fails with the error Login Failed: Invalid Username or Password.

• When you edit the value in Rule input fields, the cursor no longer jumps to the end of the string after every keystroke.

• When you try to subscribe to a Service without creating an Application first, no drop-down to select the Application is shown. This is the correct behavior.

• When you import a policy, it now correctly shows you as the owner.

• The Migration Tool can now successfully migrate published APIs or Proxies from Classic APIM to APIM 3.0.

Known Issues

• When you delete a published Service with active subscriptions, the subscribed Applications continue to show the subscription. The subscription entry for the deleted Service contains the application name undefined.

• OpenAPI specs downloaded from published Services on the Developer Portal are invalid when path parameters are incorrectly defined.

• When an API operation includes a request body schema but does not define an explicit example or examples field in the OpenAPI specification, the Request Body section does not appear when a consumer tries the endpoint in the Developer Portal.

• A Response Body with an example defined as an array can be saved, but currently can’t be edited.
  Workaround: Define a schema object that uses "type": "array" and "items": { ... } rather than using a top-level [].

Admin Manager

• In Admin Manager, the Git Integration Atlassian Bitbucket label is now updated to Atlassian Bitbucket Datacenter to indicate support for Bitbucket Datacenter APIs.

AgentCreator

Features

• Pipeline tagging for MCP Server, Agent, and Tool pipelines: Pipelines can be tagged as an MCP Server or Agent/Tool pipelines via the Pipeline Properties dialog. This makes it easy to select the available tools on behalf of your MCP Server and Agent when you use the Multi Pipeline Function Generator Snap.

Enhancements

• The Multi Pipeline Function Generator Snap now only displays tool pipelines in the dropdown. This update increases usability for creating Agents and identifying tools from standard pipelines. You can manually tag a pipeline as a tool in the Pipeline Properties tab to use this functionality.

• Support added for Background Mode in OpenAI Responses Snaps to support long-running tasks and prevent timeout errors.

• A new field has been added as part of the Agent Snap output. The sl_agent_log output field consolidates the tool response and the tool name under a single object. This streamlines the log’s record of the LLM’s reasoning process.

• Support for custom metadata in OpenAPI Function Generator and APIM Function Generator Snaps. This allows users to pass supplementary context or identifiers into the tool pipeline for downstream processing.

AutoSync

Fixed Issues

• Fixed an issue where a group member tries to access a Data pipeline shared with the group returns the following error message: Cannot read properties of undefined (reading 'username').

Designer

• When using the HTTP Client Snap, if the validation data preview exceeds the 15 MB limit, the Data Preview displays an empty array [], instead of an error message.

Git Integration

Known Limitation

• Lightweight tags created from the command line do not identify the author or contain a commit message, so can’t be used for Git checkouts for any Git provider.

  Workaround: Create tags from the GitHub, Gitlab, Azure, or Bitbucket UI instead. All tags created from a Git UI are annotated with the author and a commit message.

Monitor

Enhancements

• The Pipeline execution search in the nested view now flattens hierarchies beyond two levels, reducing the number of rows displayed to help you locate matched pipelines in complex hierarchies. The table shows the top-level parent, a placeholder row for hidden intermediate levels, and the matched pipeline, with the option to expand the placeholder to view all levels between the parent and the matched pipeline. Learn more.

  Open

  

Fixed Issues

• Fixed an issue where changing a Project’s Pipeline Validation setting to Inherit from Org Settings did not generate an entry in the Activity Log. This change is now correctly logged, ensuring complete traceability of pipeline validation configuration changes for governance and compliance.

• Fixed an issue in Monitor where the Date/Time filter on the Pipeline Executions and System overview pages accepted any characters (including special characters and arbitrarily long strings) without validation. The filter input is now validated to prevent the entry of irrelevant characters, ensuring reliable filtering of pipeline executions.

Known Issues

• Some references in the Asset Catalog and Monitor do not display updated Asset information, such as a change in Asset location.
  Workaround: Use the Asset Search.

Pipelines and Tasks

• Added support for scheduled lineage data reporting for Ultra Tasks. This is an Environment-level feature that is controlled server-side (via heartbeat). Without an active Lineage subscription, you cannot use this feature. Contact your CSM for Lineage subscription (server-side entitlement). Set the feature flag to control the push interval of lineage data. This needs to be set internally by your Environment Admin. Learn more.

Public APIs

• Introduced a new public Git commit API that returns a consistent, detailed summary of inserted, updated, deleted, and renamed SnapLogic assets across Git providers.

Snaps

New

• PDF:

  • Added the HTML to PDF Converter Snap to convert HTML sources to PDF.

Enhancements

• Azure SQL:

  • Enhanced the Azure SQL – Bulk Load Snap to correctly handle all SQL Server user-defined data types by mapping them to their base types, so pipelines can seamlessly load data into the columns of these data types.

  • Enhanced the Azure SQL - Bulk Extract Snap to enable the underlying BCP utility (v18 and above) to bypass the certification check enforced by the target SQL Server instance. This ensures the bulk data exports are not blocked because of SSL certificate issues. This change does not impact any Snaps or pipelines that use a BCP utility version below 18.

• Binary:

  • Binary Snaps that use the Azure Data Lake Gen2 OAuth2 Account now support Microsoft Fabric OneLake endpoints, such as *.dfs.fabric.microsoft.com configured in the Endpoint field, rather than using the default dfs.core.windows.net domain. Learn more.

• Kafka:

  • Enhanced the Kafka Consumer Snap with the Seek type - Earliest from timestamp that allows the Snap to read messages starting from the earliest offset or after the specified timestamp value.

• LDAP:

  • Enhanced the LDAP Snaps to support expressions in all account configuration fields, enabling dynamic runtime configuration.

• Marketo:

  • Enhanced the Marketo Bulk Extract Snap with Include record count checkbox that enables you to include the number of records processed by the export job in the output document.

• Microsoft Dynamics 365 for Sales:

  • Enhanced the Dynamics 365 OAuth2 Online Account with the Snaplex field. This enables you to configure OAuth2 authorization and refresh flows to run on a specific Snaplex.

• Salesforce:

  • Enhanced the Salesforce OAuth2 Account to support the Password and Client Credentials grant types for all Salesforce Snaps.

  • Enhanced the Salesforce Snaps (Create, Lookup, Poller, Subscriber, SOQL, Update, and Upsert), with the following retry settings that enable you to control how the Snaps handle connection and error responses.

    • Number of Retries

    • Retry Interval (seconds)

• Transform:

  • Enhanced the XML Formatter Snap to collect and report all XSD validation errors when validation is enabled. Each schema violation is now routed as a separate error document instead of stopping at the first error.

SnapGPT

Snap Copilot now automatically selects newly suggested mappings in the Mapper Snap when they have the same targetPath as existing mappings. This reduces manual selection and ensures the latest SnapGPT-generated recommendations are applied.

Open