Niftory Docs
Niftory Web3 API

Configuring Your App

The Niftory Platform gives you the ability to create and manage users without using a separate authentication system (Auth0, Firebase, etc). This is fully optional - you're always free to bring your own auth system and interact with the API directly. The best way to set up user authentication is to look at the Niftory Sample App, and how it configures the Niftory auth provider.
Each application receives two credentials which can be exchanged for auth tokens:

Client ID

The client ID is your application's username. It identifies your application and doesn't change.

Client Secret

The client secret is your application's password. It's the secret that proves that your application is really making calls, and allows your application to authenticate itself and its users.
Never share your client secret with anyone, or use it directly in code. Never commit a .env containing this secret.
It should be kept hidden from your front-end and from your users.
See the Quick Start to find out how to obtain these properties.

Authentication Endpoints

Any authentication library that supports OAuth 2.0 can integrate the Niftory authentication provider.
The information you need to set this up varies depending on the authentication library you use. If your library supports OIDC Discovery, so you can simply point it to our well-known endpoints:
Otherwise, you may need to check the above URLs to find our authorization endpoint and token endpoints.

Include your token with every API request

Whatever the type of authentication you use, you'll end up with a bearer token.
Configure your GraphQL client to pass this token in the Authorization header of every request. If you are using next-auth, you can retrieve the session token using the useSession hook.
In the backend you can use Backend Authentication to get a token, and then include it in your requests in the same way: