RQM REST API outbound calls not working since moving streams
Hello,
Recently my company decided to make a new stream and merge with the previous one in our GCM. Ever since the move to the new stream when I perform a get request I usually add "Configuration-Context: <STREAM ID>" onto my request header so I can get the correct data.
The issue I usually run into is that when I perform an outbound call with the APIs they revert back to the previous stream which in thus causes RQM to freak out and send me back to the home page since its configured to be in the new stream we have created.
How is it possible to assure that my APIs don't revert back to the previous stream when a user performs an outbound call with them?