Skip to main content
simik
Participating Frequently
Sep 21, 2023 8:29 PM UTC
Solved

Internal web API Call

Hi,

When I call a web API from another web API within the same server, the external url parameter value of the final web API iin the httppost request doesn't seem to work but I have to give the localhost url -  like this :localhost:8080/.../webapiname. Why is that and will this work in all environments? I understand it is not ideal to call this way, but I a little confused as to why the direct url is not working. 

    stefanhelzle0001
    stefanhelzle0001Answer
    Brainy
    Sep 22, 2023 6:53 AM UTC

    This looks like an issue with local DNS resolution. I suggest to contact your sys admins.

    View in thread

    10 replies

    mathieud0001
    mathieud0001
    Genius
    Sep 21, 2023 10:05 PM UTC

    I'm assuming this is for an on-premise installation? In the cloud, you can call an Appian API from within Appian with no issues.

    simikAuthor
    Participating Frequently
    Sep 21, 2023 10:52 PM UTC

    Yes, that's right, this is for on-premise.

    mathieud0001
    mathieud0001
    Genius
    Sep 22, 2023 3:35 AM UTC

    What error do you get when you use a direct url?

    stefanhelzle0001
    stefanhelzle0001Answer
    Brainy
    Sep 22, 2023 6:53 AM UTC

    This looks like an issue with local DNS resolution. I suggest to contact your sys admins.

      almuqeets268991
      almuqeets268991
      New Participant
      Apr 29, 2026 10:30 AM UTC

      This usually happens because external URLs route through DNS, public IP, and network security layers. In many setups, an SMS firewall or network firewall can block or restrict these loopback requests.

      localhost works because it bypasses those layers and stays inside the server.

      But this isn’t reliable for all environments, especially in cloud or microservices setups.
      Best practice: Avoid internal HTTP calls and use direct service communication.

      Terms & ConditionsAccessibility statement