Hi @YRathod , you’re running into one of those cases where the UI and the public API don’t fully line up.
Even though to.limitSendFrequency appears in the Marketing Emails API documentation, it is not consistently exposed in the GET responses for marketing emails.
The reason is that send frequency is not treated as a first-class, email-level property in the API. In the HubSpot UI, “Send frequency” is more of a delivery rule applied at send time, tied to marketing email settings and subscription logic, rather than a stable field stored on the email object itself.
So when you fetch a marketing email via the v3 endpoint, HubSpot will return core metadata (name, type, status, campaign, etc.), but it does not reliably include whether frequency capping was enabled or disabled. That’s why you’re not seeing to.limitSendFrequency in the response, even though it’s mentioned in the docs. This is a known mismatch between documentation and actual API behavior for marketing emails (https://developers.hubspot.com/docs/api-reference/marketing-marketing-emails-v3/guide )
At the moment, there isn’t an API-supported way to programmatically check whether send frequency was ON or OFF for a specific marketing email. If you need this information, the only reliable source is the HubSpot UI itself. Some teams work around this by enforcing frequency rules globally at the account level or by documenting send rules externally when emails are created, but that’s outside the API. Short version: you’re not missing a parameter or a scope. That field simply isn’t exposed today. Hopefully HubSpot makes this more explicit or adds proper support in the future. Hope this helps.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database
Hi @YRathod , you’re running into one of those cases where the UI and the public API don’t fully line up.
Even though to.limitSendFrequency appears in the Marketing Emails API documentation, it is not consistently exposed in the GET responses for marketing emails.
The reason is that send frequency is not treated as a first-class, email-level property in the API. In the HubSpot UI, “Send frequency” is more of a delivery rule applied at send time, tied to marketing email settings and subscription logic, rather than a stable field stored on the email object itself.
So when you fetch a marketing email via the v3 endpoint, HubSpot will return core metadata (name, type, status, campaign, etc.), but it does not reliably include whether frequency capping was enabled or disabled. That’s why you’re not seeing to.limitSendFrequency in the response, even though it’s mentioned in the docs. This is a known mismatch between documentation and actual API behavior for marketing emails (https://developers.hubspot.com/docs/api-reference/marketing-marketing-emails-v3/guide )
At the moment, there isn’t an API-supported way to programmatically check whether send frequency was ON or OFF for a specific marketing email. If you need this information, the only reliable source is the HubSpot UI itself. Some teams work around this by enforcing frequency rules globally at the account level or by documenting send rules externally when emails are created, but that’s outside the API. Short version: you’re not missing a parameter or a scope. That field simply isn’t exposed today. Hopefully HubSpot makes this more explicit or adds proper support in the future. Hope this helps.
Did my answer help? Please mark it as a solution to help others find it too.
Ruben Burdin HubSpot Advisor Founder @ Stacksync Real-Time Data Sync between any CRM and Database