🐛 Describe the Bug
At the moment, the Get installer details API does not expose the Relationship Number, which prevents us from accurately identifying the agency a customer is referring to. The only workaround today is requesting the company.readonly scope, which is not feasible if the app is intended to be installable at both the location and agency level.
📍 API Endpoint
/marketplace/app/:appId/installations
✅ Expected Behavior
We request that the Relationship Number be exposed in the Get installer details API to enable proper agency identification and significantly improve the support experience for both customers and integrators.
https://marketplace.gohighlevel.com/docs/ghl/marketplace/get-installer-details
💻 Screenshots or Code Samples
No response
Product Area
marketplace
📋 Use Case
Currently, when customers contact us about issues with their accounts, we ask them for their Agency's companyId. In practice, most customers don’t know this value. Even when we ask for the agency email, they often get confused between the email they used to sign up on our platform and the email associated with their agency. This back-and-forth creates unnecessary friction and delays, as these identifiers are not something customers are accustomed to remembering or using.
When we reach out to HighLevel support, we are typically asked for the Relationship Number. Customers are already familiar with this identifier and commonly use it to reference their agency. This becomes especially important for customers who manage multiple agencies, where the Relationship Number is the clearest and most reliable way to identify the correct one.
🚨 Why Should This Be Prioritized?
This blocks accurate agency identification, slows support resolution, increases customer confusion, and impacts users managing multiple agencies directly affecting support efficiency and customer satisfaction.
🧠 Additional Context
No response
🐛 Describe the Bug
At the moment, the
Get installer details APIdoes not expose the Relationship Number, which prevents us from accurately identifying the agency a customer is referring to. The only workaround today is requesting thecompany.readonlyscope, which is not feasible if the app is intended to be installable at both the location and agency level.📍 API Endpoint
/marketplace/app/:appId/installations
✅ Expected Behavior
We request that the Relationship Number be exposed in the
Get installer details APIto enable proper agency identification and significantly improve the support experience for both customers and integrators.https://marketplace.gohighlevel.com/docs/ghl/marketplace/get-installer-details
💻 Screenshots or Code Samples
No response
Product Area
marketplace
📋 Use Case
Currently, when customers contact us about issues with their accounts, we ask them for their Agency's
companyId. In practice, most customers don’t know this value. Even when we ask for the agency email, they often get confused between the email they used to sign up on our platform and the email associated with their agency. This back-and-forth creates unnecessary friction and delays, as these identifiers are not something customers are accustomed to remembering or using.When we reach out to HighLevel support, we are typically asked for the Relationship Number. Customers are already familiar with this identifier and commonly use it to reference their agency. This becomes especially important for customers who manage multiple agencies, where the Relationship Number is the clearest and most reliable way to identify the correct one.
🚨 Why Should This Be Prioritized?
This blocks accurate agency identification, slows support resolution, increases customer confusion, and impacts users managing multiple agencies directly affecting support efficiency and customer satisfaction.
🧠 Additional Context
No response