What is the RChilli Taxonomy API?
The Taxonomy API from RChilli is part of the Standardization/Taxonomy 3.0 suite, designed to provide intelligent, structured classification of skills and job profiles for resumes and job descriptions. It plays a critical role in enhancing search, matching, and data enrichment capabilities across HR systems.
Purpose and Capabilities
The Taxonomy API delivers:
-
Standardized data using a global taxonomy of over 3 million skills and 2.4 million job profiles.
-
Alternate names, synonyms, abbreviations, and comparable job titles or skills.
-
Ontology-based tagging, allowing better classification for Solr/Elasticsearch or internal search engines.
-
Smart suggestions for skills and job roles, improving candidate-job alignment.
For example:
-
If a resume lists “Java Developer,” the API can return related roles like “Software Engineer,” and skills like “Spring Boot,” “REST API,” etc., along with aliases and domain context.
Use Cases
-
Resume Parsing Enrichment
After parsing a resume, use the Taxonomy API to enhance the parsed output with:-
Related skill terms and roles.
-
Expanded synonyms and domain tags.
-
-
Search & Match Optimization
Improve search engine results by:-
Feeding expanded taxonomy-based keywords into Solr/Elasticsearch.
-
Mapping job-seeker or recruiter queries to relevant profiles.
-
-
Job Description Analysis
Automatically tag job descriptions with standard job titles and required skills, aligned to industry taxonomy. -
Government Database Compliance
Ensures alignment with standardized taxonomies from government databases in regions like the USA, EU, Canada, and Australia.
Maintenance & Updates
-
The taxonomy data is refreshed monthly to include:
-
New job roles and skills.
-
Updates based on global industry changes.
-
Multilingual expansions.
-
Alignment with international standards.
-
API Integration Notes
-
You must explicitly call the Taxonomy API to get real-time results such as:
-
Alternate names.
-
Intelligent recommendations.
-
Standardized terms.
-
It is not automatically invoked by the Resume or JD Parser unless specified.
Why Use It?
Improve search accuracy
Enable bias-free, structured classification
Enhance candidate-job matching
Ensure global compliance and consistency
Learn More
If you need help with implementation or use cases, feel free to contact support@rchilli.com
Comments
0 comments
Please sign in to leave a comment.