Member Authentication Guide

Overview

FieldEdge Members (Tenants) who build private, internal integrations use JWT-based authentication to securely access FieldEdge APIs. Authentication is handled through the Gobo Identity Provider (OAuth2), and access to private tenant data requires the FieldEdge Tenant ID (target_id).

Members typically build integrations for their own business and manage their own credentials.

How Members Obtain Client ID & Client Secret

Members can retrieve their app credentials directly from the FieldEdge Marketplace once their internal app has been provisioned.

Step 1 — Log in to the FieldEdge Marketplace

Navigate to:
https://dev.marketplace.fieldedge.com

If you don't have an account, use the onboarding form to request access.

Step 2 — Navigate to Applications

Go to: Apps → You will now see the application details screen.

Step 3 — Locate Your Credentials

Inside the selected application:

Client ID: Visible at all times in the application details screen.

Client Secret: Can be copied using the “Copy Secret” button.

⚠️ The secret may be visible only once — store it securely.

Step 4 — Locate Your FieldEdge Tenant ID

Your Tenant ID (target_id) is visible inside the FieldEdge Web Portal and is used during token requests.

Authentication Requirements

Members authenticate using:

client_id – from Marketplace

client_secret – from Marketplace

target_id – FieldEdge Tenant ID

Member Authentication Workflow

Member logs into the FieldEdge Marketplace.

Member opens their internal app under Applications.

Member copies the client_id and client_secret.

Member finds the Tenant ID in the FieldEdge application UI.

Member sends a token request to Auth API using these values.

Member calls FieldEdge APIs through Azure APIM using the JWT token.

Requesting a JWT Access Token

POST
https://dev.marketplace.fieldedge.com/oauth/token

{
  "client_id": "<your-client-id>",
  "client_secret": "<your-client-secret>",
  "target_id": "<fieldedge-tenant-id>",
  "grant_type": "client_credentials"
}

Success Response

{
  "access_token": "eyJhbGciOiJSUzI1NiIsInR...",
  "token_type": "Bearer",
  "expires_in": 28000
}

Calling FieldEdge APIs

Include the JWT in the request header:

Authorization: Bearer <jwt-token>

Overview#

How Members Obtain Client ID & Client Secret#

Step 1 — Log in to the FieldEdge Marketplace#

Step 2 — Navigate to Applications#

Step 3 — Locate Your Credentials#

Step 4 — Locate Your FieldEdge Tenant ID#

Authentication Requirements#

Member Authentication Workflow#

Requesting a JWT Access Token#

Success Response#

Calling FieldEdge APIs#