Skip to main content

Authentication

Connect Enterprise uses OAuth 2.0 Client Credentials flow for system-to-system (M2M) authentication. You exchange your Client ID and Secret for a bearer token, then include that token in all subsequent API requests.

Environment Isolation: Tokens generated for Development must not be reused in Production, and vice versa. Each environment requires its own dedicated credentials and produces a unique, isolated token.

How It Works​

  1. Your system sends your clientid and secret to the /v1/auth/login endpoint.
  2. The API returns a bearer token along with its expiration time and type.
  3. Include the bearer token in the Authorization header of every protected API call.
Authorization: Bearer <your_token>

Credentials​

Each Enterprise instance receives a unique Client ID and Client Secret. These are securely delivered by the PRIMO development team.

Keep credentials confidential: Never expose your Client ID or Secret in client-side code, public repositories, or logs. The security of your integration depends on keeping these values private.

Endpoint​

Method: POST

EnvironmentURL
Developmenthttps://lfs-connect-enterprise-api-dev-h7ekhqc6g0g2greg.centralus-01.azurewebsites.net/v1/auth/login
Productionhttps://lfs-connect-enterprise-api-prod-d6hrg8hrg9bphpc7.centralus-01.azurewebsites.net/v1/auth/login

Request Headers​

HeaderValue
Content-Typeapplication/json

Request Body​

{
  "clientid": "YOUR_CLIENT_ID",
  "secret": "YOUR_CLIENT_SECRET"
}

Examples​

curl --location 'https://lfs-connect-enterprise-api-dev-h7ekhqc6g0g2greg.centralus-01.azurewebsites.net/v1/auth/login' \
--header 'Content-Type: application/json' \
--data '{
  "clientid": "YOUR_CLIENT_ID",
  "secret": "YOUR_CLIENT_SECRET"
}'

Token Response​

A successful authentication returns a bearer token:

{
  "data": 
    {
      "token" : "eyJhbGciOiJSUzI1NiIsInR5..."
    },
  "errors": null
}

Use the access_token value in the Authorization header for all protected endpoints.

Scopes & Authorization​

Connect Enterprise uses scope-based authorization. Your token includes a set of scopes that define which API operations your client is permitted to perform.

Inspect your token. You can decode your JWT access token using jwt.io to inspect the granted scopes and expiration time.

Next Steps​