Email API suddenly getting rate limit errors out of the blue

[rbutler-nw]

Hello,

At my company, we use the HubSpot Email APi to send in email content and send emails via an external tool via our HubSpot account. We have been using this API with no issues for quite a few years now, but all of a sudden we are getting the following errors:

message":"The rate limit for this endpoint has been exceeded.","status":"error"

with no ryme or reason. There is no policy given in the response as to why it has been rate limited and it is causing us issues with our Editorial content emails getting sent out to our users across all of our publishing brands.

The endpoint in quesion:

marketing-emails/v1/emails/{{emailIDhere}}/publish-action

We have the API rate add-on, so we can do:

Burst: 200/10 seconds
Daily: 1,000,000
on our API calls, and we are WELL under that limit, yet we are constantly getting these errors with only a small amount of emails getting sent out if we are lucky.

We use a Private App to make these calls to our account with oAuth, and the volume of calls is in line with what we have been doing now for some qutie time. There has not been any increase that would justify this error whatsoever. Today for example, we have made just over 200 API calls, and every single one fails on that one endpoint - causing the content coming in from the external system to just sit in draft, as it fails to do the publishing/sending of the email.

[Jaycee_Lewis]

Hey, @RButler-jpi 👋 Have you opened a support ticket for this? Because this is a product issue and not something related to custom code, they should be able to triage this. If it were me, I'd include:

• the full path and link other matching dev doc, if possible
• an example request, response, and the full error body

If you've already done this, and they pointed you back here, please let me know. I am definitely not trying to bounce you around. My goal is to get this tracked and triaged efficiently. 

Talk soon! — Jaycee

[rbutler-nw]

Hi @Jaycee_Lewis , I did rasie a ticket with Support and our CRM. Support did direct me to post here, but eventually agreed to pass it on. Our CRM also got the PE team involved and it's being investigated. Thankfully today, it seems that the API is playing ball but of course keeping a close eye on things until investigations have concluded into the issue.