This documentation describes the Grindery OAuth 2.0 authentication flow and it is primarily for developers who work on apps that use Grindery platform.


A developer needs authentication to use the Grindery API (get user information, read/edit/create/delete workflows and workspaces, etc). 


The authentication flow is compliant with OAuth 2.0 standard and requires users to sign an authentication message using their metamask wallets. In a nutshell, the 

Application redirects users to the sign-in page.


The user signs-in using MetaMask wallet (extension).


The user gets redirected back to the application.


Application exchanges authentication code to the access token.


Application uses access token to get user information and make requests to the Grindery API.


Step 1: Sending users to the sign-in page


Your application should redirect users to the following URL: 

The following values should be passed as GET parameters:


If the user authorizes your app, Grindery will redirect back to your specified `

 with a temporary authentication code in a `

Step 2: Exchanging an authentication code for an access token


If all is well, exchange the authorization code for an access token by sending a POST request to 

https://orchestrator.grindery.org/oauth/token

The following values should be passed as body parameters:


If authentication code is valid, you will get these values in response:

All requests to Grindery API must be authenticated. The best way to communicate your access tokens, also known as bearer tokens, is by presenting them in a request's Authorization HTTP header:


Authorization: Bearer paste-user-access-token-here


Alternatively you can use JS client library to make requests to the API: 

https://github.com/grindery-io/grindery-nexus-client

To authenticate user with JS client, use `authenticate` method, and pass `access_token`.


https://github.com/grindery-io/grindery-nexus-client/blob/master/DOCUMENTATION.md

If the user's access token has expired, your application will need to use a refresh token, to get a new access token.


You can refresh the token by sending a POST request to 

If refresh token is valid, you will get these values in response:


Grindery OAuth 2.0

grindery

Business

Welcome

Courses

Miscellaneous

Funding and Grants

Grindery Planning Sessions: August 2022

Onboarding

gWork

Developers

Review

Partners

Active Topics

On Token Allocation

On Connectors

On Community 

On Organization

On Tokenomics

On Brand

On Roadmap 

On Validation

Co-creation Slide

Co-creation

Marketing

Funding/Investing - Inbound/Outbound

Funding/Investing

Knowledge Management_Operations

Grindery DAO Sales Process

Grindery Unified Marketing

Grindery Marketing

Grindery OKRs

Harmony DAO

The Graph

Storage

Snapshot-XMTP-Grindery