One request failed with 403 after 18 Months of continous successes

[SBräuer]

Hi,

Yesterday (September, 12th) at 06:51 to 06:58 my custom App suddenly received 403 responses for a ticket to deal association creation api call. The App was working fine since it started in April 2023 and the call has since succeeded.

I would like to know what caused the problem and if there is a need for me to regularly handle unexpected 403 responses from now on.

[SBräuer]

I didn't change the scope since its creation. And associating tickets to deals worked for more than one year. I also sent the request the day after it failed, and it succeeded.

It was a completely isolated event. I changed nothing before or after it happened.

[AddaxLab]

According to HubSpot Docs(https://developers.hubspot.com/docs/api/error-handling#:~:text=403%20Forbidden%20%3A%20returned%20wh....), 403 Forbidden: returned when the authentication provided does not have the proper permissions to access the specific URL. As an example, an OAuth token that only has content access would get a 403 when accessing the Deals API (which requires contacts access).
So, please check the permissions (scope) in your app

[SBräuer]

As I said in my other reply, the scope couldn't have been the probelm because the same request succeeded the next day without any changes. Similar requests (associating ticket and deal) worked before and after the failed requests without any issue.