Authenticating and authorizing should cause the client_id and client_secret to be stored in the session environment. This would allow the user to authenticate using aw_auth using custom client_id and client_secret arguments and have those persist for the sessions.
In particular, the order of preference might be:
If the function accepts client ID and secret arguments, use those
Else if session-level client ID and secret already exist, use those
Else check environment variables
If environment variables are not set, throw an error
aw_call_api and aw_call_data should have no default arguments, but check for variables automatically anyway
Authenticating and authorizing should cause the client_id and client_secret to be stored in the session environment. This would allow the user to authenticate using
aw_authusing customclient_idandclient_secretarguments and have those persist for the sessions.In particular, the order of preference might be:
aw_call_apiandaw_call_datashould have no default arguments, but check for variables automatically anyway