The Nobl Career Planner API follows the principles of REST, providing a straightforward and efficient way to interact with various resources. The API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

The API accepts JSON encoded user profiles and returns career tranisition predicitons.

The Nobl API uses API Keys to authenticate requests. A client_id and client_secret will be provided by the Nobl support team allowing for authentication at the /auth endpoint. Upon successful authentication, a time-limited Access Token will be received and can be used to authorize subsequent requests by including the header Authorization: {access_token}. The complete documentation of the authentication POST call is summarized below including required parameters, data formats, possible responses, and examples.

The API exposes a number of calls that allow computation of skill gaps between profile and a job as well as between two jobs. The API calls are described in detail below including their required parameters, data formats, possible responses and examples.

The API exposes a number of calls that allow computation of typical transitions between a profile and a job as well as between two jobs. The API calls are described in detail below including their required parameters, data formats, possible responses and examples.

The API exposes a number of calls that allow computation of trajectories between two jobs. The API calls are described in detail below including their required parameters, data formats, possible responses and examples.

The API exposes a number of calls that allow tagging of degrees with skills. The API calls are described in detail below including their required parameters, data formats, possible responses and examples.