Profiler supports more precise shaping of API requests in order to specifically exclude any of the normally-returned skill elements. This allows consumers of the API to determine what they do and do not need, which consequently makes the response smaller and the processing of the request quicker.
To exclude elements from the response, simply provide an exclude parameter with a comma-separated list of one or more element names that should not be in the response.
metadata
occupations
general_work_activities
intermediate_work_activities
detailed_work_activities
workplace_essentials
knowledges
knowledge_subdomains
skills
abilities
tools
This new functionality is optional. By default, both /competencies/analyze endpoints will return all data elements. To use the exclusion feature, simply provide an additional exclude parameter in the JSON body of your request:
POST /v2/competencies/analyze
{"text":"i am a welder and used welding equipment and acetylene torches","bias":0.4, "exclude":"occupations,detailed_work_activities,knowledges,abilities,tools"}
Caveat
The "flat" profile and "hierarchical" profile respond differently when asked to exclude one or more of the work_activities data elements.
For the flat profile, the response will simply exclude the specific work activities list(s) as specified in the request parameters.
For the hierarchical profile, the response will exclude the specific work activities specified as well as any sets below those in the tree. For example, asking to exclude intermediate_work_activities will exclude those as well as all detailed_work_activities. Asking to exclude general_work_activities will effectively exclude all work activity types from the response.