Handling PortalId Identification for Users in Webhook Event Data

Develop, Build & Integrate APIs & Integrations
1

Hello Community,

I’m facing a challenge with HubSpot integration, specifically in handling user identification through the PortalId when dealing with data received from webhook event subscriptions.

Here’s the scenario: when receiving data from event subscriptions via webhook, we obtain the portalId, which is the unique identifier for a user and belongs to a specific account. However, during the authentication process, when users authenticate our app with HubSpot, we only receive the refresh_token and access_token, which can be linked to a user in our database.

The issue arises when we need to correlate the received portalId from webhook events with the authenticated user in our system. Currently, we don’t have access to a user’s portalId during the authentication process or a query to retrieve all portalIds associated with a user (account). This makes it challenging to use the received portalId to identify the user in our database when processing webhook event data.

I’m curious to know if anyone has encountered a similar situation and has a recommended approach or best practices for handling this PortalId identification challenge.

Any insights or suggestions would be greatly appreciated!

Thank you.

2

Hi, @PNgoy :waving_hand: Thanks for your question! We have the Get Information for OAuth 2.0 Access Token endpoint, but I’m not 100% confident that is what you are asking for. If not, please let me know, and we can try tagging in a few of our community members who might have related experience.

Talk soon! — Jaycee