Anyone know about to.limitSendFrequency ?

YRathod
Member

I am trying to fetch to.limitSendFrequency property for marketing emails,

to know if SendFrequency was ON or OFF for an email,

But for some reason even if it shows in docs 

https://developers.hubspot.com/docs/api-reference/marketing-marketing-emails-v3/marketing-emails/get...

It is not exposed in API responce.

 

In UI when you go to Edit email > Send to >  Send frequency you can see this option if its on or off

 

Send frequency

Apply frequency cap so you don’t over-email contacts.Adjust frequency 

 

Help would be appreciated ,

Thanks,

Raj

0 Upvotes
1 Accepted solution
RubenBurdin
Solution
Top Contributor

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 Ruben Burdin
HubSpot Advisor
Founder @ Stacksync
Real-Time Data Sync between any CRM and Database
Stacksync Banner

View solution in original post

0 Upvotes
2 Replies 2
RubenBurdin
Solution
Top Contributor

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 Ruben Burdin
HubSpot Advisor
Founder @ Stacksync
Real-Time Data Sync between any CRM and Database
Stacksync Banner
0 Upvotes
SamTassey
Community Manager
Community Manager

Hello @YRathod

 

Welcome to the Community! 


I'd like to tag in some of our Top Contributors to see if they may be familiar with this. 

@GRajput, @TomM2, @GiantFocal, @SteveHTM 

 

-- Do you have any suggestions for @YRathod

Thank you! 


Sam, Community Manager 

0 Upvotes