The Data Fetch URL must currently be configured during the creation of the App and cannot be configured by the end user of the App. This is fine if the Data Fetch URL points to a multi-tenant server that is the same for all users.
In a single tenant use case, the end-user of the App must be able to configure the Data Fetch URL. This is not currently possible.
The workarounds that were provided by the HubSpot team were;
1- Create a broker service that redirects calls to each tenant
2- Ask each customer to create their own app and configure the Data Fetch URL.
Option 1 is not something that we are keen on for the following reasons:
- Point of failure: We becomes a new point of failure for customers who manage their own infrastructure. - Privacy implications: We can now potentially intercept all data returned by the Server. - Performance degradation: HubSpot data fetch requests timeout after 5 seconds. By adding a broker service as an extra hop, we’re potentially adding 2 seconds to the process thus reducing the net timeout to 3 seconds. The broker service needs to intercept the request, retrieve the portalID, lookup the portalID in a database to locate the corresponding URL and then redirect to that URL.
Option 2 is cumbersome for our customers, does not look professional and does not allow us to publish our App to the Market Place.
This is a request to allow App users to configure the Data Fetch URL to point to their own server.
