I am trying to setup a connection to Survey Monkey using Oauth 2.0. The setup is that they make a request, receive back a short lived code, then exchange that for a long term token. The issue I am having is that during the initial fetch of the short term code, Retool is passing Audience and Access_Type as parameters and Survey Monkey refuses to authorize the request because of that. Is there any way to suppress those extra parameters if they are empty?
Hey @nhilbelink! Welcome back to the forum. 
The short answer is that no, the built-in OAuth2 scheme doesn't support customization of the request's urlencoded parameters. This is a fairly common ask of users like yourself and I'll bump the internal feature request on your behalf! I'll provide an update here as soon as I hear anything on this end.
In the meantime, you can replicate the exact same authorization process - and tweak the individual steps to your needs - using the "Custom Auth" option, instead.
You can find a walkthrough of this feature here. The way the SurveyMonkey docs are written should make replicating this fairly straightforward, which is very convenient.
Don't hesitate to follow up here if there's anything else we can help with!
A post was split to a new topic: Aspera Faspex API does not permit some parameters during OAuth2 flow
