The Nobl ESCO classification 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 job descriptions and returns ESCO code predictions. Suggested ESCO codes can also be added to job descriptions.

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 for the addition or updating of resources such as jobs and ESCO codes. Next, each of these API calls are described in detailed including their required parameters, data formats, possible responses and examples.

Exposes functionalities for fetching the ESCO codes of jobs. More specifically, a GET method allows users to obtain the ESCO codes of a job with given job_id. The API calls are described in detail below including their required parameters, data formats, possible responses and examples.