# Marketing V3 Emails API

**URL:** <https://community.hubspot.com/t/marketing-v3-emails-api/143683>\
**Category:** APIs & Integrations\
**Tags:** professional\
**Created:** [December 4, 2025, 10:29am UTC](https://community.hubspot.com/t/marketing-v3-emails-api/143683 "2025-12-04T10:29:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ISergeyssels](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isergeyssels/32/48852_2.png) [@ISergeyssels](https://community.hubspot.com/u/ISergeyssels)\
**Post date:** [December 4, 2025, 10:29am UTC](https://community.hubspot.com/t/marketing-v3-emails-api/143683/1 "2025-12-04T10:29:21Z")

</div>

Hello Community,

We are facing a critical blocker when trying to use the Marketing V3 Emails API (GET /marketing/v3/emails), which consistently results in a **403 Client Error: Forbidden** with the error message **MISSING\_SCOPES**.

### The Core Problem: Inability to Configure Scopes

The Super Admin attempted to enable the required **content** scope in the Private App configuration but **received a permission error** stating they are unauthorized to add that specific scope to the app.

This confirms that the **content** scope is currently **NOT** enabled on the app, but the inability to enable it appears to be a permissions/licensing issue beyond the Super Admin role.

### Configuration Status:

1. **Required Scope:** The **content** scope is required for the V3 Emails API.
2. **Scope Status:** The app **fails to save with the content scope enabled** due to a permissions error experienced by the Super Admin.
3. **User Role:** The user attempting to modify the app is a **Super Admin**.
4. **API Call Status:** The API call fails with **MISSING\_SCOPES** because the required scope cannot be added.
5. **Support Contact:** HubSpot Support confirmed no issues with the initial setup and referred us here.

### Question:

Since the Super Admin is explicitly blocked from adding the **content** scope to the app, what are the possible root causes?

- Does the ability to grant the **content** scope require a **specific HubSpot Marketing Hub product tier (e.g., Professional or Enterprise)** that our account may lack?
- Is there a different Admin permission needed beyond “Super Admin” to manage high-level scopes like content?

We need to understand the license or permission requirement that is blocking the Super Admin from saving this scope. Thank you!

---

<div class="post-metadata">

**Author:** ![BrandonWoodruff](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/brandonwoodruff/32/61045_2.png) [@BrandonWoodruff](https://community.hubspot.com/u/BrandonWoodruff)\
**Post date:** [December 4, 2025, 2:15pm UTC](https://community.hubspot.com/t/marketing-v3-emails-api/143683/2 "2025-12-04T14:15:48Z")

</div>

Based on [HubSpot’s own docs](https://developers.hubspot.com/docs/apps/legacy-apps/authentication/scopes), the **content** scope is tied to CMS Hub Pro/Enterprise _or_ 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.

A couple quick things to validate:

- The content scope covers emails, pages, blog, campaigns — so HubSpot only exposes it to portals with the matching product tier.
- Super Admin rights don’t override licensing restrictions, so the block can happen even if permissions are otherwise correct.
- Sometimes checking another related scope (e.g., CMS) can confirm whether the limitation is tier-based.

To help narrow this down: **Which HubSpot subscription tier is your portal currently on?**

Let me know if this helps, or if you have any other questions!

* * *

✔ Was I able to help answer your question? Help the community by **marking it as a solution.**

| ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/3/d314478a36473977ed45320812b9331d25e0d3c4.jpeg) | **[Brandon Woodruff](https://www.linkedin.com/in/brandon-woody-woodruff/)**  
Senior Software Developer @ [Pearagon](https://www.pearagon.com/)Still have questions? Reach out at [brandon@pearagon.com](mailto:brandon@pearagon.com) ![](https://d2qpr2jzcazej7.cloudfront.net/original/3X/d/c/dcad77e6cf96145dd117147531ae4423b9b5cd91.png) |

* * *

---

<div class="post-metadata">

**Author:** ![ISergeyssels](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/isergeyssels/32/48852_2.png) [@ISergeyssels](https://community.hubspot.com/u/ISergeyssels)\
**Post date:** [December 4, 2025, 2:24pm UTC](https://community.hubspot.com/t/marketing-v3-emails-api/143683/3 "2025-12-04T14:24:43Z")

</div>

We have a Marketing Hub Professional subscription.

---

<div class="post-metadata">

**Author:** ![SteveHTM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/stevehtm/32/22074_2.png) [@SteveHTM](https://community.hubspot.com/u/SteveHTM)\
**Post date:** [December 5, 2025, 2:38pm UTC](https://community.hubspot.com/t/marketing-v3-emails-api/143683/4 "2025-12-05T14:38:43Z")

</div>

@ISergeyssels - 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.

I have tried in various account I have access to - it seems I can set ‘content’ scope without a Marketing Pro subscription but with a Data Hub subscrioption - but I cannot set marketing email without that Marketing Hub Pro subscription.

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.

Hope you can figure this out.

Steve
