-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature]: Function to send request from pre-request script #2205
Comments
Thank you for reporting. We will consider this during the planned revamp of the Scripting System. |
Send request is a missing great feature, please, can you priorize this? 🥺 |
Yup, I am working on a solution for this, stay tuned! |
@AndrewBastin Any news on this? |
@AndrewBastin Any news? |
Please discuss about this in the RFC discussion #2292 for the scripting API revamp. We are working on a scripting API revamp to support for more complex use cases. |
Any update guys. can we get CSRF token in Pre-request scripts now ? We really need it's to test Laravel |
Would like to add my +1 support for this feature, as it is making it difficult for me to migrate from Postman. My Use Case: A pre-request script that handles creation of OAuth 2.0 client_credentials grant access token before the request, then stores both the access token and expiration in environment variables. I have been using this in postman before Postman even added OAuth 2 support, and it's a great way to get around the lack of Hoppscotch support for OAuth 2.0 client_credentials grant (see #874) It would be really great if these pre-request scripts could then be stored at the collection level and shared. |
Why was this issue closed? |
Is there an existing issue for this?
Summary
Postman provides method
sendRequest
to make AJAX request from pre-request script. For example:This feature is useful when you need to get for example xsrf-token,
Why should this be worked on?
Allow testing API's build with Laravel Scout to get xsrf-token. I think it's much more use cases than this one.
The text was updated successfully, but these errors were encountered: