Skip to main content

​
System Requirements

The TechWolf Skill Sync integration will make use of existing Degreed functionality. The customer will need a TechWolf contract with a live TechWolf tenant. This TechWolf tenant must be populated with (a subset of) the worker’s entities in Degreed.

​
Degreed Configuration

A Degreed API key must be configured in the Degreed tenant with the appropriate scopes for skill synchronization. The integration follows the steps outlined in the Degreed Getting Started with the API and Authentication Guide documentation.

​
API URL Configuration

The API base URL depends on your environment (betatest or production) and data center (US, EU, or CA):
Data CenterEnvironmentAPI Base URL
USBetatesthttps://api.betatest.degreed.com/
USProductionhttps://api.degreed.com/
EUBetatesthttps://api.eu.betatest.degreed.com/
EUProductionhttps://api.eu.degreed.com/
CAProductionhttps://api.ca.degreed.com/

​
Token Endpoint Configuration

The OAuth token endpoint URL depends on your environment and data center:

​
degreed.com Domain

Data CenterEnvironmentToken URL
USBetatesthttps://betatest.degreed.com/oauth/token
USProductionhttps://degreed.com/oauth/token
EUBetatesthttps://eu.betatest.degreed.com/oauth/token
EUProductionhttps://eu.degreed.com/oauth/token
CABetatesthttps://ca.betatest.degreed.com/oauth/token
CAProductionhttps://ca.degreed.com/oauth/token

​
degreed.app Domain

Data CenterEnvironmentToken URL
USBetatesthttps://<your-organization>.beta.degreed.app/oauth/token
USProductionhttps://<your-organization>.degreed.app/oauth/token
EUBetatesthttps://<your-organization>.eu.beta.degreed.app/oauth/token
EUProductionhttps://<your-organization>.eu.degreed.app/oauth/token
CABetatesthttps://<your-organization>.ca.beta.degreed.app/oauth/token
CAProductionhttps://<your-organization>.ca.degreed.app/oauth/token
The access token base URL is not the same as the API base URL used to submit requests.

​
API Key Setup

Follow these steps to create an API key for the TechWolf Skills integration. These steps follow the process outlined in the Degreed Getting Started with the API documentation.
You must be a Technical Admin with the “Manage API Keys” permission to create API keys in Degreed. If you don’t have this permission, contact your Degreed Technical Solutions Specialist.

​
1. Log in to Degreed

Access your Degreed tenant using your administrator credentials.

​
2. Access Admin View

In the left sidebar menu at the bottom, press “Show admin view” to access administrative functions. Show Admin View

​
3. Navigate to API Keys

In the integrations menu item, go to “API keys” to access the API key management interface. Integrations API Keys

​
4. Create New API Key

Press “Create new” to start the API key creation process. Create New API Key

​
5. Configure API Key

Give your API key a memorable name and select the scopes required for this integration to work:
  • user_skills:read
  • user_skills:write
  • skill_ratings:read
  • skill_ratings:write
API Key Configuration 1 API Key Configuration 2
When creating API keys, use minimal viable scopes. These scopes indicate the endpoints accessible to access tokens created with the API key. As a general data security principle, Degreed recommends using a minimal number of scopes to enable your integration work to succeed.

​
6. Secure Credentials

Note down the client secret securely - you will only be able to see this once. Also note down the client ID for future reference. API Key Credentials
The client secret is only displayed once during API key creation. Make sure to store it securely as it cannot be retrieved later. If lost, you will need to create a new API key.

​
TechWolf Configuration

The TechWolf tenant will be configured by TechWolf itself.
  1. In the integration service on the TechWolf side, TechWolf adds the credentials of the customer-created API key. For this, the customer will need to share the following values with TechWolf:
    • The API base URL (see the API URL Configuration section)
    • The OAuth token endpoint URL (see the Token Endpoint Configuration section)
    • The client ID and client secret of the API key (see Step 6 of the API Key Setup section)
    • A test Employee ID for validation testing
  2. TechWolf adds TechWolf API credentials with correct scopes to have access to the TechWolf API and links that TechWolf tenant to the Degreed tenant.
  3. TechWolf validates API access by adding and removing a skill and proficiency for the test Employee.
  4. TechWolf runs an initial sync of user profiles with the TechWolf API and sets up the tenant configuration to start the sync process.

​
Configuration Options

​
Sync Direction Settings

The integration supports three sync direction options:
  • Bidirectional (bidirectional): Two-way sync between TechWolf and Degreed (default)
  • To TechWolf (to_techwolf): Skills flow from Degreed to TechWolf only
  • To External (to_external): Skills flow from TechWolf to Degreed only

​
Merge Strategy Options

  • Merge Systems (merge_systems): Combines skills from both systems, TechWolf takes precedence
  • Push TechWolf (push_techwolf): Replaces all Degreed skills with TechWolf data
  • Push External (push_external): Replaces all TechWolf skills with Degreed data

​
Proficiency Scale Configuration

  • Configurable: N-point scale (1-N), where N is an integer corresponding to the customer’s Degreed setup
  • Setting: degreed_maximum_proficiency_level tenant configuration
  • Note: Scales always start at 1, not at 0

​
User Identifier Types

  • Employee ID (employee-id): Customer-defined identifier (default)
    • Uses the employee_id field from API responses
    • Customer-defined identifier that matches between systems
  • User ID (user-id): Degreed-generated identifier
    • Uses the user_id field from API responses
    • Degreed’s internal user identifier

​
Deployment Tasks & Responsibilities

  1. TechWolf: Setup Skill Sync environment and tenant requirements
  2. Customer: Create API key based on workflow described above.
  3. Customer: Share API key credentials with TechWolf:
    • Client ID
    • Client Secret
    • Token URL (OAuth endpoint)
    • API URL (API base URL)
    • Test Employee ID (for validation testing)
  4. TechWolf: Validate API access by adding and removing a skill and proficiency for the test Employee
  5. TechWolf: Run initial sync of user profiles with TechWolf API.
  6. TechWolf: Setup tenant configuration and start sync process based on configured direction.
  7. Customer: Check end-user test scenarios.