Create your application
Last updated
Last updated
Accessible through your Matrica Business Dashboard at , under the "OAuth2" tab.
Once you are onboarded as a community with Matrica, you will be able to create an application that will allow you to set up the OAuth 2.0 flow.
Your application can be set as "Public" or "Private". An application is considered "Public" if the flow is started from a public client (such as a mobile app or SPA) which cannot store any confidential data. A "Private" application will be issued a Client Secret which will be required on the authorization and token API calls for extra security.
Your application will have multiple fields related to the OAuth 2.0 flow:
Client ID: should be considered public information.
Client Secret: only if your app is set to "Private".
Redirect URIs: you will need to set your callback URIs, localhost URIs won't be accepted.
Scopes: the list of scopes that your application needs and will be asked to the user.
You will also be able to set up a name, description, image and a link to your ToS for your application. This data will be shown to the user on the Authorization screen after triggering the OAuth 2.0 flow.
You will need to define the scopes that your application needs. Keep in mind that the lowest amount of scopes you ask for, the most likely the user will accept the OAuth 2.0 authorization. For example, if you ask for their socials and your app only needs their NFTs to operate, the user might refuse to link their account to your application.
Available scopes:
profile: Get the user profile information, including username, profile picture and banner, creation date
wallets: Get the user 's wallet addresses. Will include cross-chain wallets when they will be available on Matrica (ETH, etc...).
nfts: Get the user's NFTs. It's not equivalent to getting the wallets as the user could link multiple wallets without NFTs in them.
socials.discord: Get the user's linked discord id.
socials.twitter: Get the user's linked twitter id.
socials.telegram : Get the user's linked telegram id.
email : Get the user's verified email.
Notes:
a minimum of one scope must be required by your app.
if a scope is scheduled to be removed by Matrica, we will announce a deprecation warning beforehand.
more scopes might be added in the future.
