RChilli JD Parser

PAID
By RChilli Inc | Updated 25์ผ ์ „ | Text Analysis
Health Check

N/A

Followers: 2
Resources:
Product Website Terms of use
API Creator:
Rapid account: R Chilli Inc
RChilli Inc
rchilli-inc
Log In to Rate API
Rating: 4 - Votes: 2

README

JD Parser API

RChilli JD Parser API is an intelligent software that extracts parameters from a Job Description and saves the information in the required attributes already defined.

The parser analyses a JD created in DOC, DOCX, PDF, RTF, TXT, ODT, HTM and HTML, DOCM, DOTM, DOT, DOTX, MHT formats.

It processes job descriptions or vacancies in real-time. RChilli uses AI/ML trusted technologies to lexically parse a job description into the JSON output format.

With the implementation of Taxonomy in JD Parser, it is now fully compliant with search engines like Solr or Elasticsearch and enhances its search capabilities.

Use Cases of OurJD Parser

  • Parse job descriptions in multiple languages

  • Upload a job description and get the output in JSON format

  • Parse job descriptions from a single or multiple email inboxes

  • Parse multiple job descriptions in one go and get the structured data

  • Improve search results by indexing its taxonomy ontologies to Solr/Elasticsearch

  • Create a structured job post for the internal job posting

  • Extract all the job information from the job feeds

How Our JD Parser Helps?

  • Enhance candidate experience by showing clear job descriptions to candidates

  • Scale operations through structured job data extracted from the job feed

  • Enhance your search capabilities

  • Get job data from emails in a structured format in seconds

Language Support

RChilli JD Parser supports parsing of multiple languages, it does not require any separate configuration. The parser auto-identifies the languages of the JD and extracts the information.

The JD Parser supports the following languages, to know more, see https://www.rchilli.com/languages.

  • Arabic (Right to Left)

  • Chinese (Simplified)

  • Dutch

  • English

  • French

  • German

  • Indonesian

  • Italian

  • Japanese

  • Polish

  • Portuguese

  • Russian

  • Spanish

  • Turkish

JD Parser Endpoints, Method, and Parameters

The endpoints indicate how you access the resource, while the method indicates the allowed interactions (such as GET, POST, or DELETE) with the resource.

JD Parser Endpoint

The JD Parser API endpoint returns the JD data in JSON format. There are two JD parser endpoints as mentioned below:

  • Parsing by JD Text : JD Parser API allows you to parse JD text in base64 format, the API used:
    /ParseJDText

  • Parsing by JD Binary Data : JD Parser API allows you to parse JD using binary data in base64 format, the API used:
    /ParseJD

Method

The JD Parser API uses only POST method.

Request Headers

Header Data Type Description
Content-Type string Indicates the input type of the incoming request body. The only supported value is application/json.

Parameters

Different Parameters are needed in the JSON request format based on the input data type.

1. Parsing by JD Text : When the JD text is parsed in base64 format, the parameters must be given as follows:

Parameter:-

  • Base64Text (String): JD text in base64 format

2. Parsing by JD Binary Data : When the JD is parsed using binary data in base64 format, the parameters must be given as follows:

Parameter:-

  • FileData (String): JD file binary data in base64

  • FileName (String): JD filename with extension (eg. JdSoftwaredeveloper.doc)

Error Code & Error Message

This topic lists the error codes of the JD Parser.

Error Code Error Message
400 Bad Request
401 Unauthorized
403 Forbidden
404 NOT FOUND
405 METHOD NOT ALLOWED
429 TOO MANY REQUESTS
500 SERVER ERROR
503 SERVICE NOT AVAILABLE
1004 File name with file extension is required
1008 Not Text Content
1009 JD File Extension Not Supported
1014 Corrupted data/ No Content Found
1015 Unable to parse the content
1016 No JD Content Found
1018 File size is too large for processing
1019 Unable to detect language
1020 Unable to open PDF Parser
1021 File conversion error