Problem with Activity Login endpoint

Developer Support APIs & Integrations
1

Hi guys, everyday I’m getting a 500 status response from a specify endpoint
/account-info/v3/activity/login

{"status":"error","message":"There was a problem with the request.","correlationId":"e94c338a-b2d7-4d2f-9568-56b1b9aa0ff4"}

I don’t think is AWS as we are doing a some request that we get 200 response, only this one is not working, as you can see bellow.

image (5).png
image (5).png1113×175 28 KB

2

Hi @Niuco,

Thanks for reaching out and including a screenshot of the error message!

Can you please provide screenshots of the request you’re sending? This will help the community to better assist with next steps.

Thank you!

Best,

Kristen

3

Hi Kristen,

We hide the auth token because it is confidential data.

This request was made on 2022-10-13 16:20.

request:

curl --location --request GET 'https://api.hubapi.com/account-info/v3/activity/login' \
--header 'Authorization: Bearer CKru####################################################################################################################################################################################################AFoA'

response:

{
 "status": "error",
 "message": "There was a problem with the request.",
 "correlationId": "f53cc5a0-9501-4ac4-8ed9-f7dccb9fb305"
}
4

Hi @Niuco,

Thanks for reaching back out with the additional information and for hiding the sensitive data!

I noticed that the example “GET” endpoint on this Activity Login API doc here does not include location.

Screen Shot 2022-10-17 at 5.12.44 PM.jpg
Screen Shot 2022-10-17 at 5.12.44 PM.jpg896×826 62.8 KB

Could you try removing -- location -- from your request and sending it to HubSpot again?

Best,

Kristen

5

Hi Kristen,

Unfortunately the problem still persists. Something we noticed during testing is that there seems to be a “cold start Problem” on your side. Because whenever we send the first request we receive the error 500. But on the second attempt the data is received normally. The error occurs both with the --location tag and without it.
The problem occurs at any time of the day, whenever there is a gap of 15-20 minutes between one request and another.

2022-10-20_09h36_06.jpg
2022-10-20_09h36_06.jpg1983×345 115 KB

2022-10-20_10h14_59.jpg
2022-10-20_10h14_59.jpg1438×436 122 KB

6

Hi @Niuco,

Thank you for your patience. The Account Activity API is in beta which means there are improvements being made to it.

This is odd indeed - so just to confirm you get the error on one call, and then on the second attempt, you can make the call successfully?

Are you using the same request and getting the same response for both calls?

Thank you,

Kristen

7

- Yes

- Yes

8

Thank you for the details, @Niuco!

I’ll reach out to the team and reply to this thread when I have an update.

Best,

Kristen

9

Hi @Niuco,

We are not able to reproduce this on our end.

Can you verify and try the following please?

  • Ensure that the authorization token is correct
  • Try to test this in Postman (free API tool) to see if it behaves differently.

Thank you,

Kristen

10

Hi, is there any feedback on our request?

11

Hi Kristen,

We hide the auth token because it is confidential data.

This request was made on 2022-10-13 16:20.

request:

curl --location --request GET 'https://api.hubapi.com/account-info/v3/activity/login' \
--header 'Authorization: Bearer CKru####################################################################################################################################################################################################AFoA'

response:

{
 "status": "error",
 "message": "There was a problem with the request.",
 "correlationId": "f53cc5a0-9501-4ac4-8ed9-f7dccb9fb305"
}