Version 2026.40
1 new11 changed1 retiring7 fixed
DoorDash Ads¶
With this release, a new DoorDash Ads connector has been added, enabling the import of campaign performance, product sales, and category share reporting. This expands data integration options for CPG brands and other advertisers.
Amazon Marketing Cloud¶
With this release, the Amazon Marketing Cloud connector has been updated to align with a new 365-day refresh token expiration policy. Proactive re-authorization prompts have been implemented to prevent data interruptions, and expired tokens are now gracefully handled with user-friendly error messages. For more information, see Amazon Marketing Cloud: Setup guide and the announcement.
Barb¶
With this release, the Barb connector has been updated to API version 3, providing access to the latest features and improved stability.
Facebook Ads¶
With this release, the workflow for updating Facebook Ads ad creatives and their permanent URLs has been reworked to significantly improve performance and efficiency. This leads to faster synchronization and reduced API usage.
Walmart Connect¶
With this release, the Walmart Connect connector has been enhanced to allow data collection for multiple advertiser IDs within a single datastream. This improves efficiency and flexibility while ensuring data security through robust validation, and each extract now includes advertiserId and advertiserName columns. For more information, see Walmart Connect: Setup guide.
Warehouse Manager¶
With this release, access to the Warehouse Manager is now determined directly by the warehouse configuration, simplifying its availability management.
Web Connect¶
With this release, support for body parameters in the Access Token URL has been added for Web Connect (OAuth2), resolving daily re-authorization issues for APIs requiring these parameters. Additionally, a value table variable used both in the URL and in a header or the request body now takes the same value in each place, instead of every combination being requested. For more information, see Web Connect: Setup guide.
MCP default schema mappings¶
With this release, MCP exposes full management of source-level default schema mappings through new actions to list, create or update, and remove default mappings for a connector type, backed by the new /api/default-schema-mappings/ Management API endpoint. For more information, see Configuring Data Mapping in Management API.
MCP write preview messages¶
With this release, MCP write previews show human-readable confirmation messages and resolved entity names, such as connection names, instead of internal IDs, making it clearer what a pending write will do before it is confirmed.
Smart pulling: Management API v2 merged into v1¶
With this release, smart pulling configuration with the full multi-range range_spec is available on Management API v1, and the separate v2 API has been removed. Clients that used /api/v2/ should call the same paths under /api/v1/. This is a breaking change: PUT /api/v1/datastreams/pulling/smart/ now requires range_spec and no longer accepts frequency and refresh_range in the request body, and unknown fields in the body are rejected. GET /api/v1/datastreams/ still returns frequency and refresh_range, alongside range_spec. For more information, see Managing pulling mode and smart schedule in Management API.
Full management of smart pulling is now also available through MCP. The fetch_write tool has gained two new actions, set_pulling_mode (to switch between smart and custom schedule) and configure_smart_pulling (to manage range_spec, is_active, deadline, and start), and fetch_search(list_schedules) now returns complete scheduling information for both smart pulling and custom schedules. These MCP actions need the datastream:read and datastream:write scopes.
Walmart Connect authorization fields renamed¶
With this release, Walmart Connect authorizations created or updated through the /api/connection-types/{type_id}/connections/ endpoints take search_advertiser_ids and display_advertiser_ids instead of search_advertiser_id and display_advertiser_id, which each took a single integer. The new fields are strings that hold one advertiser ID or a comma-separated list of IDs, and responses now include them. The old field names are no longer recognized: a request that still sends them succeeds, but the advertiser IDs in them are not saved. Existing authorizations were migrated automatically. This is a breaking change for clients that create or update Walmart Connect authorizations through the Management API. For more information, see Walmart Connect: Setup guide.
Warehouse schema quoting hint¶
With this release, the Management API warehouse schema endpoint (GET /api/v1/workspaces/{workspace_id}/warehouse/schema/) returns a new hint field with guidance on quoting column names. Additionally, unquoted column names that match a known column are now quoted automatically when running a query on a Snowflake warehouse, and the warehouse query timeout has been increased from 30 to 45 seconds. These changes apply where the warehouse query API is enabled. For more information, see Querying warehouse data in Management API.
Adtraction¶
With this release, all datastream templates for the Adtraction Advertiser connector have been removed. Users will no longer have access to pre-configured templates and will need to set up datastreams manually or use custom configurations.
Resolved issues¶
With this release, issues have been resolved for the following connectors and destinations:
Adright
Amazon Advertising
Facebook Ads
Netbase
Outbrain
SEMRush
SQL Database destination
X Public Basic (Twitter)
Default schema mapping error handling¶
With this release, creating or updating a default mapping on /api/target-columns/{id}/mappings/ returns HTTP 400 when the source field or the target column is already mapped for that source type, or when the target column does not exist. Previously, a duplicate target column or an unknown target column made a create return HTTP 200 with an error body and an update return HTTP 500. If a concurrent request creates the same mapping first, the request returns HTTP 409. A create whose target_column_id differs from the target column in the URL now also returns HTTP 400, instead of creating the mapping under the other column. For more information, see Configuring Data Mapping in Management API.
Management API destination permissions¶
With this release, Management API keys with the destination:write scope can again create, update, and delete destinations, for example with POST /api/target-types/{ct}/targets/. A recent regression had returned HTTP 403 for these requests. A key can only create a destination in, or move it to, a workspace that the key can access.
MCP datastream workspace ID¶
With this release, MCP datastream tools return the correct workspace_id when getting or creating a datastream, instead of null.
MCP login error¶
With this release, after a rejected API key or an expired login session, the MCP login page tells you to start again from your MCP client, instead of showing a form that could only fail with “Invalid request. Please refresh the page and try again.”
MCP OAuth security fix¶
With this release, a security vulnerability in the MCP OAuth authorization flow has been resolved.
MCP security fix¶
With this release, a security vulnerability in the MCP server has been resolved.