Linkfire utilizes OAuth 2.0 for authentication and authorization. The reason we use OAuth 2.0 is so that your integration does not need to store or send any Linkfire user login credentials. If OAuth 2.0 is unfamiliar territory for you, we highly recommend reading this introduction article to OAuth 2.0 by Digital Ocean.
By default, Linkfire API supports the OAuth 2.0 client_credential flow.
Scope
In order to authenticate with the API you need to specify the public.api scope in the request body when requesting your Bearer token. You can do this by making a POST request to https://auth.linkfire.com/identity/connect/token with your assigned API credentials.