Can a pre-script trigger a different request?

[ttelford]

I've looked around in the documentation, but haven't found an answer: This is similar to the request about chaining requests from a year or so ago.

• Are we able to use Scripting to trigger (send) a different request from our collection(s)? If so, what is the specific code / method to use to "Trigger collection/request in a pre-script?

For example, a common usage pattern I have is:

• Request "A" retrieves an API token (such as an OAuth token).
• Request "B" is used to query if a provided API token is valid.

It's simple enough to use scripting to run "A" manually, and then put that OAuth token to a variable for use in subsequent requests ("B" or "C"). Then I can manually run "B" and/or "C".

My question is if there's a way to (manually) trigger request "C" - (and I know scripting lets me do some validation) - and then request "C" uses scripting to automatically trigger request "A" and/or "B" as needed?

With pseudo-code along the lines of:

• Is there an OAuth token set?
  • If no, trigger request "A" to retrieve the token.
• If yes trigger request "B" to verify if the token is valid
  • if no, trigger request"A" to retrieve a new token
• If yes, trigger allow request "C" to continue

[darrenburns]

There's no way to programmatically send requests at the moment. Maybe one day, but it's unlikely I'll be able to add this any time soon.