Becoming a Provider in the Degreed EcoSystem

How to Become a Provider

When integrating content into Degreed, integrating organizations will first need a “Provider” record within the Degreed ecosystem. This Provider record serves as the basis for all other related objects and access. A provider record cannot be created without assistance from Degreed. The following must be provided to create a provider record:

  • 400x400 .PNG image for a logo within the Degreed UI
  • Desired title for the provider record (typically the name of the integrating organization)
  • Suitable “visit link” url

The process requires interaction with a Degreed Technical Consultant and takes 5-8 business days to complete. Be sure to discuss the integration method before submitting your request so that appropriate FTP repositories can be established during the same process if needed.

Why You Need to Become a Provider

Content items contain a “provider” attribute. This attribute reflects which provider that content originates from. If no provider value is present, the content is considered to be part of the internal catalog of that organization. Largely, internal catalogs contain internal documents and material - company intranet information, shared documents, policies, and sometimes even internal LMS content.

Provider content is generally held for content represented through integrations. In most instances, an integrator should use a provider value on their content integrated into a Degreed organization. However, this is not a hard rule. Here are some points to consider when deciding if your content should be internal to the customer organization in question, or provider content:

  • Users enjoy clicking on the hyperlinked provider name in various places in the Degreed UI to yield all results from that provider. If there is no provider value on your content, this functionality would not be present.
  • Degreed customers generally prefer that their internal catalogs are reserved for truly internal documents, as this makes a clear distinction for users to understand what content to expect, and where.
  • Integrator branding is typically a user-consumption selling point.
    If a file integration is used, the content is branded with the provider name and code by default, as by virtue of the script, a provider is already determined. However, when integrating through API, the credentials given by the customer admin may be an “organization API key” or a “provider API key.” If your integration is only about content, required-learnings, and completions, then you need a "provider API key". If you will need to access other data such as users' skills or recommended-learnings, you will need the fuller access enabled by an "organization API key". This is because an organization API key may open up scopes that leave the customer’s users’ private data susceptible to inappropriate access, and because most integrations do not require endpoints that contain user data, such as the users endpoint. For more information, see the Users endpoint.