OAuth 2.0 Flow

This guide explains how your platform logs in FYERS users and gets an access token for each of them.

USE CASE

Set up login for a platform where FYERS clients use your app with their own accounts.

Details

This is a simple OAuth 2 Authentication Flows.
This is recommended for applications which have a backend server which can authenticate the second step
This is not recommended for Single Page Applications (SPA)
The flow has two steps: Step 1, User Authorization (the redirect returns the auth_code and state to your redirect_uri; see Authorization Code); Step 2, Generate Access Token.
Third-party apps are created for platform providers. To create a common app, contact [email protected].
The user logs in with their own FYERS credentials and is redirected to your redirect_uri with an auth_code.
The resulting access_token expires daily at 6:30 AM; send it as app_id:access_token in the Authorization header.
Diagram