Skip to main content
Quick Summary: The legacy REST API was deprecated in 2025. This guide outlines the key differences in access, authentication, and response format to help you plan your migration to the new GraphQL API.
SkillsDB has shifted from the legacy platform, which was deprecated in 2025. If you using the legacy API, please refer to the points below in your planning migration to the new GraphQL API. This document outlines the key differences between the legacy REST API and the new GraphQL API for SkillsDB, highlighting usage, consumption patterns, and access endpoints to assist developers during migration.
  • Access - Base URL
    • REST API (Legacy): https://***api.azurewebsites.net/Service1.svc
    • GraphQL API (New): The Production and Staging URLs of our GraphQL APIs can be found on our GraphQL schema page. You need to be a user on the SkillsDB app to view the docs.
  • Request Format
    • REST API (Legacy): Multiple HTTP endpoints per resource
    • GraphQL API (New): Single endpoint with flexible queries / mutations
  • Authentication
    • REST API (Legacy): Token via POST /login using APICode
    • GraphQL API (New): JWT signed by client, Validated with public key
  • Response
    • REST API (Legacy): Fixed shape per endpoint
    • GraphQL API (New): Client-defined structure

​
Authentication/Authorization:

  • On the legacy API access there used to be a login to obtain bearer access token, which is:
    • POST - {baseURI}/login with payload of :- 
      {
    /// Get this API Key from your company skills db portal (Only Administrator can get this information.)
    "APICode":"{{API_Key}}"
}
  • On the new GraphQL APIs you will be managing/signing JWT token with your private key and provide us the public key to validate the JWT. For more details please look into this Authentication documentation.

​
Need Help?

If you run into any issues or have questions, reach out to your organization’s SkillsDB administrator or contact SkillsDB Support.