OAuth 2.0 flow in the Make API
This guide explains how to integrate Make into your application using OAuth 2.0 authorization. For general OAuth 2.0 concepts, refer to the OAuth 2.0 protocol specification.
Before implementing OAuth 2.0, you must register your OAuth 2.0 client with Make's authorization server to obtain:
Client ID (required for all clients)
Client Secret (only for confidential clients)
Supported protocols
OIDC (OpenID Connect): Simplified user authentication
PKCE (Proof Key for Code Exchange): Enhanced security for public clients (mandatory for SPAs and mobile apps)
API Endpoints
Endpoint
URL
Authorization
Revocation
OpenID discovery
PreviousRequesting an OAuth 2.0 clientNextAuthorization code flow with refresh token (confidential clients)
Last updated