Skip to main content
auroraj5980
New Participant
Jan 29, 2024 10:14 AM UTC
Solved

Web Service return token

Hello everyone!
I have to do a web service for the first time.
This web service will receive a response with a token that I must use in the next call to obtain the information I want.
Could someone guide me to do this? Do I need two web services; one to receive the touch and another once I already have the token to receive the response?

    8 replies

    harshitb6843
    Brainy
    Jan 29, 2024 10:24 AM UTC

    This looks like two sequential calls. You can just have two different integrations configured to do their respective works and then you can call the first one and use the response of it as input for the second one. 

    Are you facing any problems configuring it?

    auroraj5980
    New Participant
    Jan 29, 2024 11:07 AM UTC
    ​
    Thank you very much, I don't really know how I could implement it. Would you be so kind as to tell me how to do it?
    harshitb6843
    Brainy
    Jan 29, 2024 11:12 AM UTC

    Sure. Tell me where do you want to use it? In a process model or on an interface.

    Here is a quick documentation on how you can call an integration - docs.appian.com/.../Call_an_Integration.html

    mathieud0001
    Genius
    Jan 29, 2024 12:15 PM UTC

    What kind of service are you trying to call? Normally, these steps can (and should be) taken care of by the Connected System. In this case, you'll likely be storing access tokens within the process itself which could be a security issue.

    auroraj5980
    New Participant
    Jan 30, 2024 7:28 AM UTC

    I have to call a web service, collect the token it returns and integrate it into the next call that will return the information I need in my process. I'm considering using appian's "web API" for the calls. maybe you could do it with one connected system and two integrations?The problem is to collect that token and take it to the next integration

    mathieud0001
    Genius
    Jan 30, 2024 1:07 PM UTC

    Yeah, that is a common pattern. Auth token vs access token.

    Would be 1 connected system that handles getting both and 1 integration. This way, your access token is not in plaintext in your process.