Built-in apps
HTTP
OAuth 2.0 authentication type
4 min
oauth 2 0 authentication type is used when the service provider requires client credentials like client id and client secret create a connection for the oauth 2 0 authentication type to make http(s) requests that require an oauth 2 0 authorization, you must create an oauth connection first for that, you need an app/ service account access to a developer portal or settings a redirect uri (sometimes called a callback url) app/ service credentials obtain credentials in the app create an oauth client in the app that you want to connect with {{product name}} to do this, enter the developer portal or settings specify a redirect uri https //www integromat com/oauth/cb/oauth2 obtain client credentials those are usually called client id and client secret, but can also be defined as app key and app secret, or another way save the client credentials in a safe place you will need them when building a scenario in make find the authorize uri and token uri in the app's api documentation these are the addresses through which make communicates with the app create a connection in make once you've got the required credentials from the app, you can select oauth 2 0 as an authentication type in the http > make a request module, click create connection , and fill in the required fields field description connection name enter the name for your connection flow type s elect the flow authorization code (requires entering an authorize uri and token uri from the service's api documentation) implicit (requires entering the authorize uri from the service's api documentation) scopes add api scopes refer to the service's api documentation to find the required scopes client id enter the credentials you saved from your app/ service client secret enter the credentials you saved from your app/ service in the advanced settings , you can also configure field description scope separator select scope separator comma or space space is the standard separator when multiple scopes are requested in a url query parameter, the space is url encoded as %20 or +, e g , scope=read%20write%20profile comma is a common non standard separator some service providers accept or even require this separator in the request , e g , scope=read,write,profile authorize parameters if needed, enter additional authorization request parameters as a key value pair access token parameters if needed, e nter additional access token request parameters as key value pairs refresh token parameters if needed, e nter additional refresh token request parameters as key value pairs access token setup custom headers specify any custom headers to send in the request access t oken placement select whether to send the token in the header , query parameters , or both t oken name enter the name of the authorization token in the header the default value is bearer you can https //help make com/connect an application#tn2pj at any moment in the connections section for that click connections in the left sidebar click three dots > edit next to the required oauth connection you will see the edit window add or remove scopes, edit available authentication parameters, and click save all the modules that use this connection will be automatically adjusted http request examples with the oauth 2 0 authentication you can see how to use the http > make a request module with the oauth 2 0 authentication in these articles https //help make com/call google apis with oauth 20 http request https //help make com/connect to any web service using oauth 20