Workforce data · Occupational skills, tasks, and competency data API
Power job-to-skill matching, technical persona discovery, or a developer-tool onboarding recommender by mapping occupations to tasks, knowledge, skills, and crosswalks. Strong for HR-tech, learning, recruiting, workforce intelligence, and developer-skills products that need a standardized occupation/skill ontology.
Put it to work
Power job-to-skill matching, technical persona discovery, or a developer-tool onboarding recommender by mapping occupations to tasks, knowledge, skills, and crosswalks. Strong for HR-tech, learning, recruiting, workforce intelligence, and developer-skills products that need a standardized occupation/skill ontology.
Use the available employment or skills categories to refine audience research. Check how closely those categories match the people who evaluate or buy your product.
What it covers
Geography: Use the geography stated by the source; coverage can vary by dataset and release.
Granularity: Power job-to-skill matching, technical persona discovery, or a developer-tool onboarding recommender by mapping occupations to tasks, knowledge, skills, and crosswalks.
Source type: Occupational skills, tasks, and competency data API
Access and cost
REST API returning JSON; developers must register for access, and the service documents authentication, rate limits, pagination, and licensing.
Cost: Current price was not established in this review; check the provider's access terms.
Update cadence: Release cadence was not normalized in this review; check the source's dates, update notes, and API limits before comparing periods.
Before you use it
API access requires registration and is governed by O*NET Web Services licensing; do not assume unrestricted bulk redistribution merely because the data is publicly viewable.; U.S. occupational framework and SOC-linked data; it is not a globally representative labor-skill census, although crosswalks can connect to other classifications.; O*NET releases/database versions change over time; API results represent the service's current version and should be version-aware for reproducible analytics.