<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Qlik Stitch: Marketo Integration and the access_token change in 2026 in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Marketo-Integration-and-the-access-token-change-in/ta-p/2535361</link>
    <description>&lt;P data-unlink="true"&gt;The goal of this article is to address the upcoming changes&amp;nbsp;announced by Marketo&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;regarding the deprecation of authentication via the&amp;nbsp;access_token query parameter, which will no longer be supported after January 31, 2026. For further details, please refer to:&amp;nbsp;&lt;A href="https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication?lang=en#using-an-access-token" target="_self"&gt;Using an Access Token | Marketo Developer Guide&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Marketo specificities: "If your project uses a query parameter to pass the access token, it should be updated to use the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication?lang=en#using-an-access-token" target="_blank" rel="noopener"&gt;Authorization header&lt;/A&gt;&amp;nbsp;as soon as possible. New development should use the Authorization header exclusively".&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The Stitch Marketo integration (V2) already handles authentication using access tokens, as outlined in Marketo’s documentation.&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;Specifically, Stitch includes a Bearer token in the&amp;nbsp;Authorization header of its API calls. This approach complies with Marketo’s authentication requirements, so no additional configuration is needed on your end.&lt;/P&gt;
&lt;P&gt;For reference, please visit the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://github.com/singer-io/tap-marketo/blob/9a2849ebbb4238fca83ab0a87d5e100ffa6b97fc/tap_marketo/client.py#L124" target="_self"&gt;integration's repository | github.com&lt;/A&gt;.&lt;/P&gt;</description>
    <pubDate>Thu, 06 Nov 2025 08:24:31 GMT</pubDate>
    <dc:creator>David_Apodaca</dc:creator>
    <dc:date>2025-11-06T08:24:31Z</dc:date>
    <item>
      <title>Qlik Stitch: Marketo Integration and the access_token change in 2026</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Marketo-Integration-and-the-access-token-change-in/ta-p/2535361</link>
      <description>&lt;P data-unlink="true"&gt;The goal of this article is to address the upcoming changes&amp;nbsp;announced by Marketo&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;regarding the deprecation of authentication via the&amp;nbsp;access_token query parameter, which will no longer be supported after January 31, 2026. For further details, please refer to:&amp;nbsp;&lt;A href="https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication?lang=en#using-an-access-token" target="_self"&gt;Using an Access Token | Marketo Developer Guide&lt;/A&gt;.&lt;/P&gt;
&lt;P&gt;Marketo specificities: "If your project uses a query parameter to pass the access token, it should be updated to use the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://experienceleague.adobe.com/en/docs/marketo-developer/marketo/rest/authentication?lang=en#using-an-access-token" target="_blank" rel="noopener"&gt;Authorization header&lt;/A&gt;&amp;nbsp;as soon as possible. New development should use the Authorization header exclusively".&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;The Stitch Marketo integration (V2) already handles authentication using access tokens, as outlined in Marketo’s documentation.&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/STRONG&gt;Specifically, Stitch includes a Bearer token in the&amp;nbsp;Authorization header of its API calls. This approach complies with Marketo’s authentication requirements, so no additional configuration is needed on your end.&lt;/P&gt;
&lt;P&gt;For reference, please visit the&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://github.com/singer-io/tap-marketo/blob/9a2849ebbb4238fca83ab0a87d5e100ffa6b97fc/tap_marketo/client.py#L124" target="_self"&gt;integration's repository | github.com&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Nov 2025 08:24:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Stitch-Marketo-Integration-and-the-access-token-change-in/ta-p/2535361</guid>
      <dc:creator>David_Apodaca</dc:creator>
      <dc:date>2025-11-06T08:24:31Z</dc:date>
    </item>
  </channel>
</rss>

