Skip to main content
Open

Access Base Url from Web Connection

Related products:FME FormFME FlowTransformers
  • Jul 30, 2025 7:18 PM UTC
  • 2 replies
  • 65 views

philipv
Contributor
Forum|alt.badge.img+2

In my experience, web service credentials and the base url for a web service go hand in hand.  For example, if I have credentials for a sandbox instance of a service, that would go along with a sandbox base url (ex. https://sandbox.servicename/api/v2 or https://servicename/sandbox/api/v2 )

But I have found that the pre-built web services do not prompt for a base url.

I realize that I can add a prompt by creating my own Web Service, but how would I access my Base Url parameter within the Request URL in the HTTPCaller?

My idea is:

  • Prompt for endpoint base url by default in all Web Services (to be entered while creating a new Web Connection).
  • In the HttpCaller transform, rename the “Use Authentication” checkbox to “Use Authentication / Web Connection”
  • In HttpCaller, move Request Url below the checkbox
  • If there is a non-empty endpoint base url defined in the selected Web Connection, Add a “« base url” marker into the Request Url textbox 
  • The user can then complete the endpoint (i.e. /employees )

The benefit of this feature is that I can have multiple workspaces all using the same Web Connection, and if either the URL or the credentials change, I can modify this once in FME Flow without having to alter any workspaces in FME Form.

2 replies

jennaatsafe
Safer
Forum|alt.badge.img+5
New→Open

philipv
Contributor
Forum|alt.badge.img+2
  • Author
  • Contributor
  • Nov 17, 2026 6:32 PM UTC

To hopefully boost my argument, consider the “FME Flow” web service which contains a parameter for the “FME Flow URL” (FME_SERVER_SERVR) which it uses to get credentials to connect to an FME Flow instance.  If one uses that connection within an HTTPCaller, it would be appropriate to use that same base URL to form the Request URL rather than hardcoding it, or using a Deployment Parameter.

If one used a Deployment Parameter and it did not match the “FME Flow URL”, the call will fail.  Why force the developer to define the base URL in two different places when they must match?