<?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>topic Re: Marketing V3 Emails API in APIs &amp; Integrations</title>
    <link>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231099#M85932</link>
    <description>&lt;P&gt;We have a&amp;nbsp;&lt;SPAN&gt;Marketing Hub Professional&amp;nbsp;subscription.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 04 Dec 2025 14:24:43 GMT</pubDate>
    <dc:creator>ISergeyssels</dc:creator>
    <dc:date>2025-12-04T14:24:43Z</dc:date>
    <item>
      <title>Marketing V3 Emails API</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231019#M85927</link>
      <description>&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;We are facing a critical blocker when trying to use the Marketing V3 Emails API (GET /marketing/v3/emails), which consistently results in a &lt;STRONG&gt;403 Client Error: Forbidden&lt;/STRONG&gt; with the error message &lt;STRONG&gt;MISSING_SCOPES&lt;/STRONG&gt;.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;The Core Problem: Inability to Configure Scopes&lt;/H3&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The Super Admin attempted to enable the required &lt;STRONG&gt;content&lt;/STRONG&gt; scope in the Private App configuration but &lt;STRONG&gt;received a permission error&lt;/STRONG&gt; stating they are unauthorized to add that specific scope to the app.&lt;/P&gt;&lt;P&gt;This confirms that the &lt;STRONG&gt;content&lt;/STRONG&gt; scope is currently &lt;STRONG&gt;NOT&lt;/STRONG&gt; enabled on the app, but the inability to enable it appears to be a permissions/licensing issue beyond the Super Admin role.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;Configuration Status:&lt;/H3&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Required Scope:&lt;/STRONG&gt; The &lt;STRONG&gt;content&lt;/STRONG&gt; scope is required for the V3 Emails API.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Scope Status:&lt;/STRONG&gt; The app &lt;STRONG&gt;fails to save with the content scope enabled&lt;/STRONG&gt; due to a permissions error experienced by the Super Admin.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;User Role:&lt;/STRONG&gt; The user attempting to modify the app is a &lt;STRONG&gt;Super Admin&lt;/STRONG&gt;.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;API Call Status:&lt;/STRONG&gt; The API call fails with &lt;STRONG&gt;MISSING_SCOPES&lt;/STRONG&gt; because the required scope cannot be added.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;&lt;STRONG&gt;Support Contact:&lt;/STRONG&gt; HubSpot Support confirmed no issues with the initial setup and referred us here.&lt;/P&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;H3&gt;Question:&lt;/H3&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Since the Super Admin is explicitly blocked from adding the &lt;STRONG&gt;content&lt;/STRONG&gt; scope to the app, what are the possible root causes?&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;Does the ability to grant the &lt;STRONG&gt;content&lt;/STRONG&gt; scope require a &lt;STRONG&gt;specific HubSpot Marketing Hub product tier (e.g., Professional or Enterprise)&lt;/STRONG&gt; that our account may lack?&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Is there a different Admin permission needed beyond "Super Admin" to manage high-level scopes like content?&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;We need to understand the license or permission requirement that is blocking the Super Admin from saving this scope. Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 10:29:21 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231019#M85927</guid>
      <dc:creator>ISergeyssels</dc:creator>
      <dc:date>2025-12-04T10:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: Marketing V3 Emails API</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231092#M85930</link>
      <description>&lt;P&gt;Based on &lt;A href="https://developers.hubspot.com/docs/apps/legacy-apps/authentication/scopes" target="_blank" rel="noopener"&gt;HubSpot’s own docs&lt;/A&gt;, the &lt;STRONG&gt;content&lt;/STRONG&gt; scope is tied to CMS Hub Pro/Enterprise &lt;EM&gt;or&lt;/EM&gt; Marketing Hub Pro/Enterprise. If your portal isn’t on one of those tiers, the Private App won’t let a Super Admin enable that scope at all, which lines up with the “unauthorized” error you’re seeing.&lt;/P&gt;&lt;P&gt;A couple quick things to validate:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;P&gt;The content scope covers emails, pages, blog, campaigns — so HubSpot only exposes it to portals with the matching product tier.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Super Admin rights don’t override licensing restrictions, so the block can happen even if permissions are otherwise correct.&lt;/P&gt;&lt;/LI&gt;&lt;LI&gt;&lt;P&gt;Sometimes checking another related scope (e.g., CMS) can confirm whether the limitation is tier-based.&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;To help narrow this down: &lt;STRONG&gt;Which HubSpot subscription tier is your portal currently on?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Let me know if this helps, or if you have any other questions!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;P&gt;&lt;SPAN class="lia-unicode-emoji"&gt;&lt;SPAN class="lia-unicode-emoji"&gt;&lt;span class="lia-unicode-emoji" title=":heavy_check_mark:"&gt;✔️&lt;/span&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;Was I able to help answer your question? Help the community by&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;STRONG&gt;marking it as a solution.&lt;/STRONG&gt;&lt;/P&gt;&lt;TABLE width="100%"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD width="20.365535248041773%" height="191px"&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="BrandonWoodruff_0-1764857732423.jpeg" style="width: 400px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/163144iFF648762F2D1BA47/image-size/medium?v=v2&amp;amp;px=400" role="button" title="BrandonWoodruff_0-1764857732423.jpeg" alt="BrandonWoodruff_0-1764857732423.jpeg" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;TD width="79.50391644908615%" height="191px"&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A href="https://www.linkedin.com/in/brandon-woody-woodruff/" target="_blank" rel="noopener nofollow noreferrer"&gt;Brandon Woodruff&lt;/A&gt;&lt;BR /&gt;&lt;/STRONG&gt;Senior Software Developer @&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://www.pearagon.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;Pearagon&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Still have questions? Reach out at&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="mailto:brandon@pearagon.com" target="_blank" rel="noopener nofollow noreferrer"&gt;brandon@pearagon.com&lt;/A&gt;&lt;/P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="BrandonWoodruff_1-1764857732362.png" style="width: 200px;"&gt;&lt;img src="https://community.hubspot.com/t5/image/serverpage/image-id/163143i998D81CB3F6212EA/image-size/small?v=v2&amp;amp;px=200" role="button" title="BrandonWoodruff_1-1764857732362.png" alt="BrandonWoodruff_1-1764857732362.png" /&gt;&lt;/span&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;HR /&gt;</description>
      <pubDate>Thu, 04 Dec 2025 14:15:48 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231092#M85930</guid>
      <dc:creator>BrandonWoodruff</dc:creator>
      <dc:date>2025-12-04T14:15:48Z</dc:date>
    </item>
    <item>
      <title>Re: Marketing V3 Emails API</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231099#M85932</link>
      <description>&lt;P&gt;We have a&amp;nbsp;&lt;SPAN&gt;Marketing Hub Professional&amp;nbsp;subscription.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 14:24:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231099#M85932</guid>
      <dc:creator>ISergeyssels</dc:creator>
      <dc:date>2025-12-04T14:24:43Z</dc:date>
    </item>
    <item>
      <title>Re: Marketing V3 Emails API</title>
      <link>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231470#M85955</link>
      <description>&lt;P&gt;&lt;a href="https://community.hubspot.com/t5/user/viewprofilepage/user-id/183406"&gt;@ISergeyssels&lt;/a&gt;&amp;nbsp;- This looks like it may be an wonky commercial decision by HubSpot. I'm frankly very surprised that this API requires a 'content' scope rather than a 'marketing email' scope and I don't find the documentation of this very clear.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have tried in various account I have access to - it seems I can set 'content' scope&amp;nbsp; without a Marketing Pro subscription but with a Data Hub subscrioption - but I cannot set marketing email without that Marketing Hub Pro subscription.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I would have expected that content scope would be tied to a Content Hub subscription - but that does not appear to be the case. It seems like something like that is what you are bumping into.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Hope you can figure this out.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Steve&lt;/P&gt;</description>
      <pubDate>Fri, 05 Dec 2025 14:38:43 GMT</pubDate>
      <guid>https://community.hubspot.com/t5/APIs-Integrations/Marketing-V3-Emails-API/m-p/1231470#M85955</guid>
      <dc:creator>SteveHTM</dc:creator>
      <dc:date>2025-12-05T14:38:43Z</dc:date>
    </item>
  </channel>
</rss>

