Hello, is there any way to do this? What I need is to set a global environment variable based on a response of token refresh call. This token is then used to authenticate in other gRPC calls.
I am able to do this in Postman, but I’d like to migrate to Apidog, this functionality is crucial for me though.
In Postman this is done with “After response” script, see the attached Postman screenshot.
If there is another way how to save the accessToken to global environment variable after calling the showed Refresh call, I’d like to learn that.
Thank you very much.
You can utilize Post-processor Scripts. Please refer to the following link for more information: Post processor scripts - Apidog Docs
Additionally, you can use the pm Object API to retrieve the response object and save it as a global variable. You can find more details here: Postman scripts reference - Apidog Docs
Apologies for the misunderstanding. Currently, the gRPC project does not support the use of post-processor scripts. You will need to manually copy and parse the value in the Environment management panel.
Hello Karan, thanks for the reply, I was worried it will be so. Are you one of the devs or affiliated anyhow? Is the implementation of post-processor scripts for gRPC on the roadmap and will it be implemented anytime soon? It is a real deal-breaker right now, we can’t afford to manually copy the token to environment management panel every signle time (the token is very short lived and hour team works on a micro-service architecture with dozens of services that authenticate by this value).
Apidog looks very promising and impressive but having any way of setting the env var from the response of gRPC call is absolutely crucial. Insomnia, Kreya, Postman, all of these clients are capable of it, but they don’t suite us for one reason or another; Apidog seems great, but this one crucial feature is missing.
Yukio Ikeda can I please get any time estimate on this feature, if it is even planned? Thanks
It’s in the product plan roadmap. But it’s not scheduled yet. Sorry for the late reply, because we are still seeing internally if this can be supported first.
