API oauth assign engagement to account

Developer Support APIs & Integrations
1

Three questions:

1. Is the oAuth authentication for the API only for the super admin OR for indivudual accounts under the super admin?

2. If it is only one for the super admin, how do we assign an engagement (like a phone call) to a specific account (that made or received the call) through the API? The test accounts don’t seem to have any uniquie id, or email to use.

3. If it is only for the super admin then whey won’t it give us the access token for the super admin but does it only when we choose a speficific test account?

We couldn’t find a clear answer in any of the docs regarding these questions.

Thanks.

2

Hi, @AKhan92 :waving_hand: Thanks for reaching out.

  1. OAuth cannot be set up for individual Users when creating your app. There isn’t an option to define only for Super admin, for example.
  2. Which version of the Engagements API are you using? The Legacy Engagements API endpoints (stable and supported) or the v3 Engagements API endpoints? For example, with the v3 endpoints, there is a parameter called hubspot_owner_id, which corresponds to, and allows you to, associate the Engagement to a specific User.
  3. Can you give the community more details on this question?

Best,

Jaycee

3

Hi Jaycee,

Thank you so much for replying so quickly.

1. Thanks for clarifying that, we thought that as well but were not sure at all.

2. Because of point 1, we obviously would need an engagement, say a call, to be associated with a user because each user does not have their unique token but share the main one as mentioned in point 1. The confusion is that, in the testing accounts hubspot provides, there is no email set for each testing account. That’s why you can’t use the email, for example, to get the owner id of the testing account 1, say, or testing account 2. So now we try to find the owner id with an email address and hope that when we use the real accounts that it will find those account owner id’s based on the email and associate the calls to those correct users.

3. This point is a little subtle. As mentioned in point 1, there is only one oauth that needs to be obtained. one would assume that account to be the developer account, which all the testing accounts can then share. But you have to select one of the testing accounts (as if choosing one of the users) in order to get the oauth. Maybe again, it could be the testing environment quirk and may work correctly when we use the actual accounts eventually.

Thanks and best regards,