Overview of the flow OAuth2 Flow ReceiptHero
Initiate the flow by redirecting the user to the ReceiptHero consent page.
If the user approves the request then the authorization server will redirect the user to the redirect URI defined in the request.
To use the state parameters, the state is to be defined in JSON and encoded into Base64.
The client must make sure that the state matches the provided state value provided to the authorization endpoint. This protects against CSRF type of attacks. The code expires one minute after it has been created.
The client sends the previously received authorization code to the token endpoint which then returns an access token.
The request can be made in either application/json or application/x-www-form-urlencoded.
The returned access token is a JSON Web Token.
In Token you get ID for this connection.
Authorization: Bearer <USERS_OAUTH_TOKEN>
HTTP 200 OK
Response Not Found
HTTP 404 Not Found
It is possible to update an existing OAuth2 connection by using this dedicated view.
The user is redirected back with the following query string parameters: