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:
Required Scope: The content scope is required for the V3 Emails API.
Scope Status: The app fails to save with the content scope enabled due to a permissions error experienced by the Super Admin.
User Role: The user attempting to modify the app is a Super Admin.
API Call Status: The API call fails with MISSING_SCOPES because the required scope cannot be added.
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!
Based on HubSpot’s own docs, 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 bymarking it as a solution.
@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.
@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.
Based on HubSpot’s own docs, 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 bymarking it as a solution.