RChilli Search and Match

RChilli Search & Match API allows you to search and match candidates and jobs with great relevancy and accuracy than simple database searching and matching algorithms.

It filters resume data according to global industry-standard ontologies and taxonomies. You can search Resume or JD based on your search keyword out of the total Resumes and JDs indexed. The lightning-fast cluster computing technology of Search & Match Engine will help you get the perfect candidate through normalized and enriched data e.g. skills/competency, domain, location, education, city, company, and job title.

Search and Match Use Case

Follow the below use cases of the Search and Match:

• Get similar job recommendations matching a job (Job to Jobs)

• Get more job recommendations to the candidate (Resume to Jobs)

• Get more candidate recommendations for a job position (Job to Resumes)

• Get similar candidate recommendations matching a resume (Resume to Resumes)

• Convert any search string to a qualified search query by tagging location, company, skill, job profile, experience level, tools, language, etc.

• Enhance the user experience by showing the recommended skills/job titles to the candidate/recruiter while searching.

• Refine your search with Faceting/Filters

• Avoid indexing duplicate records in search engines through de-duplication

How Search and Match Helps

The Search and Match help users as follows:

• A smarter approach to reach the right candidate by recognizing, filtering, and ranking talent

• Find the perfect candidate through skill mapping, domain, location, education, city, company, and job title

• Get all search keywords separately for a more refined result of your query a through query analyzer

• Broaden the scope of your search capabilities

• Get perfect candidates similar to the searched candidates within a fraction of time

• Show highly relevant top 10 candidates to the recruiters

• A safe backup with a GDPR compliant Search & Match engine

• Get a more productive recruiting system

Search and Match API 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.

The Search and Match API uses POST method.

1. Parse and Index API

To search Resume’s and JD’s using RChilli Search and Match API, you require to parse the Resume/JD and index them.

In one Search and Match API call, the document is parsed (using RChilli Resume Parser /RChilli JD Parser ) and indexed. The indexing provides operations for managing the indexes. This includes adding and updating the index as well as removing from it and rebuilding it.

API Endpoint

The Parse and Index API uses the below endpoint:
/parseAndIndex

API Method

The Parse and Index API uses only POST method.

API Request Type

The Parse and Index API uses JSON request type.

API Request Header

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

API Parameters

The Parse and Index API requires the following parameters in the JSON request format:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
id	String	Set unique index ID so that it can correlate with your data	Required
fileContent	String	Provide file content in base64 format	Required
fileName	String	Name of the file with the extension	Required
deduplication	Object	DeDuplication helps to avoid indexing duplicate records in search engine.	Optional

Note:

To update the index of a document, simply call this method using index ID of the document to be updated.

Before parse and indexing of the documents, the following are required:

• Resumes

• Job Descriptions

2. Simple Search API

The Simple Search API method empowers you to make your document searchable with a string query without specifying search parameters.

In Simple Search API call, you get candidates - Score (out of 100), FullName, CurrentJobProfile, CurrentEmployer, TotalExperienceInYear, City, State, Country, id (Index).

API Endpoint

The Simple Search API uses the below endpoint:
/simpleSearch

API Method

The Simple Search API uses only POST method.

API Request Type

The Simple Search API uses JSON request type.

API Request Header

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

API Parameters

The Simple Search API requires the following parameters in the JSON request format:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
keyword	String	Text query contains entities like job profile, skill, location or organization, etc.	Required
facet	Object	For more details on facets, check Facets	Optional
sorting	Object	For more details on sorting, check Sorting	Optional
filter	Object	For more details on filters, check Filter	Optional
geoSearch	Object	For more details on geoSearch, check Geographical Search	Optional
explainScore	Boolean	Default is false. If set true this returns details about how a document is searched. For more details, check Explain Score	Optional
explainScoreType	String	Default is text. It can be set as JSON and work if ExplainScore is true. For more details, check Explain Score	Optional
pageSize	Int	Number of records return in one API call, default is 50. For more details, check Pagination	Optional
pageStart	Int	Start index of record to return. Can be used for paging when multiple record are searched. Default is 0. For more details, check Pagination	Optional
excludeDocumentIds	Array	Document Ids which you don’t want to consider in search.	Optional

Note:

Before searching documents, you only require to index documents using Parse and index API.

3. Boolean Search API

In the Boolean (advance) Search, unlike Simple Search, you can customize your search by specifying search parameters like - Job Profile, Company, Degree, etc.

Boolean Search gives more flexibility in searching by specifying required/optional search parameters. You can search values for multiple fields with multiple values. Multiple values are searched based on the OR conditions. Multiple Fields are searched in the required conditions on the basis of AND condition while in the optional condition it is search with OR condition.

API Endpoint

The Boolean Search API uses the below endpoint:
/booleanSearch

API Method

The Boolean Search API uses only POST method.

API Request Type

The Boolean Search API uses JSON request type.

API Request Header

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

API Parameters

The Boolean Search API requires the following parameters in the JSON request format:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
query	String	Put keywords for searching resume/JD	Required
required	Object	JSON of fields with list values. Multiple fields are search with AND condition. while their multiple values search with OR condition.	Required
optional	Object	JSON of fields with list values. Multiple fields are search with OR condition. while their multiple values search with OR condition.	Required
facet	Object	For more details on facets, check Facets	Optional
sorting	Object	For more details on sorting, check Sorting	Optional
filter	Object	For more details on filters, check Filter	Optional
geoSearch	Object	For more details on geoSearch, check Geographical Search	Optional
explainScore	Boolean	Default is false. If set true this returns details about how a document is searched. For more details, check Explain Score	Optional
explainScoreType	String	Default is text. It can be set as JSON and work if ExplainScore is true. For more details, check Explain Score	Optional
pageSize	Int	Number of records return in one API call, default is 50. For more details, check Pagination	Optional
pageStart	Int	Start index of record to return. Can be used for paging when multiple record are searched. Default is 0. For more details, check Pagination	Optional
excludeDocumentIds	Array	Document Ids which you don’t want to consider in search.	Optional

4. Match API

This API find Resumes/Job Descriptions matching your input documents.

There are four types of matching cases as follows:

• Resume to Resume : Get resumes from the index which matches the input resume.

• Resume to JD : Get Job Descriptions from the index which matches the input resume.

• JD to JD : Get Job Descriptions from the index which matches the input Job Descriptions.

• JD To Resume : Get resumes from the index which matches with input Job Descriptions.

API Endpoint

The Match API uses the below endpoint:
/match

API Method

The Match API uses only POST method.

API Request Type

The Match API uses JSON request type.

API Request Header

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

API Parameters

The Match API requires the following parameters in the JSON request format:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
docType	String	Name of Index type Resume/JD	Required
jsonData	String	RChilli Parser API JSON output data in base64	Required
explainScore	Boolean	Default is false. If set true this returns details about how a document is searched. For more details, check Explain Score	Optional
explainScoreType	String	Default is text. It can be set as JSON and work if ExplainScore is true. For more details, check Explain Score	Optional
pageSize	Int	Number of records return in one API call, default is 50. For more details, check Pagination	Optional
pageStart	Int	Start index of record to return. Can be used for paging when multiple record are searched. Default is 0. For more details, check Pagination	Optional
excludeDocumentIds	Array	Document Ids which is not consider in search.	Optional
sorting	Object	For more details on sorting, check Sorting	Optional

5. Match with ID API

This API find Resumes/Job descriptions matching your input documents ID’s.

There are four types of matching cases as follows:

• Resume to Resume : Get resumes from the index which matches the input resume.

• Resume to JD : Get Job Descriptions from the index which matches the input resume.

• JD to JD : Get Job Descriptions from the index which matches the input Job Descriptions.

• JD To Resume : Get resumes from the index which matches with input Job Descriptions.

API Endpoint

The Match with ID API uses the below endpoint:
/matchWithId

API Method

The Match with ID API uses only POST method.

API Request Type

The Match with ID API uses JSON request type.

API Request Header

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

API Parameters

The Match with ID API requires the following parameters in the JSON request format:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
docType	String	Type of the file i.e Resume/JD	Required
jsonData	String	RChilli Parser JSON output data in base64	Required
matchId	String Array	List of document ID’s you want to match from the indexed database	Required
explainScore	Boolean	Default is false. If set true this returns details about how a document is searched. For more details, check Explain Score	Optional
explainScoreType	String	Default is text. It can be set as JSON and work if ExplainScore is true. For more details, check Explain Score	Optional
pageSize	Int	Number of records return in one API call, default is 50. For more details, check Pagination	Optional
pageStart	Int	Start index of record to return. Can be used for paging when multiple record are searched. Default is 0. For more details, check Pagination	Optional
sorting	Object	For more details on sorting, check Sorting	Optional

6. One To One Match API

This API matches the candidate CV with the JD. The API responds the detailed matching score once the candidate CV matches with the JD.

API Endpoint

The One To One Match API uses the below endpoint:
/oneMatch

API Method

The One To One Match API uses the only POST method.

API Request Type

The One To One Match API uses JSON request type.

API Request Header

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

API Parameters

The One To One Match requires the following parameters in the JSON request format:

Name	Type	Description	Remarks
resumeContent	String	Provide resume/CV file content in base64 format	Required
resumeFileName	String	Name of the resume/CV file with the extension	Required
jdContent	String	Provide JD file content in base64 format	Required
jdFileName	String	Name of the JD file with the extension	Required
matchType	String	Resume to JD / JD to Resume	Required
explainScore	Boolean	Default is false. If set true this returns details about how a document is searched. For more details, check Explain Score	Optional
explainScoreType	String	Default is text. It can be set as JSON and work if ExplainScore is true. For more details, check Explain Score	Optional

7. Get Document Ids API

This API is used to get all the indexed document ID’s.

API Endpoint

The Get Document Ids API uses the below endpoint:
/getDocumentIds

API Method

The Get Document Ids API uses only POST method.

API Request Type

The Get Document Ids API uses JSON request type.

API Request Header

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

API Parameters

To execute Get Document Ids API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
pageSize	Int	Number of records return in one API call, default is 50. For more details, check Pagination	Optional
pageStart	Int	Start index of record to return. Can be used for paging when multiple record are searched. Default is 0. For more details, check Pagination	Optional

8. Get Document Detail API

This API is used to get a particular indexed document detail by providing document ID.

API Endpoint

The Get Document Details API uses the below endpoint:
/getDocumentDetail

API Method

The Get Document Details API uses only POST method.

API Request Type

The Get Document Details API uses JSON request type.

API Request Header

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

API Parameters

To execute Get Document Details API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
pageSize	Int	Number of records return in one API call, default is 50. For more details, check Pagination	Optional
pageStart	Int	Start index of record to return. Can be used for paging when multiple record are searched. Default is 0. For more details, check Pagination	Optional

9. Delete API

This API is used to delete indexed files, from the database, by providing document ID.

API Endpoint

The Delete API uses the below endpoint:
/delete

API Method

The Delete API uses only POST method.

API Request Type

The Delete API uses JSON request type.

API Request Header

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

API Parameters

To execute Delete API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
id	String Array	List of document ID’s you want to delete from the indexed database	Required

10. Spell Checking API

If you give any wrong input while searching, this API will check and correct it.

API Endpoint

The Spell Checking API uses the below endpoint:
/spellCheck

API Method

The Spell Checking API uses only POST method.

API Request Type

The Spell Checking API uses JSON request type.

API Request Header

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

API Parameters

To execute Spell Checking API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
keyword	String	Mention the keyword	Required
fieldType	String	Mention the fieldType like JobProfile/Skill	Required

11. Delete All Documents API

This API is used to delete all indexed files from the database.

API Endpoint

The Delete All Documents API uses the below endpoint:
/deleteAllDocs

API Method

The Delete All Documents API uses only POST method.

API Request Type

The Delete All Documents API uses JSON request type.

API Request Header

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

API Parameters

To execute Delete All Documents API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required

12. Analyze API

The Analyze query is an extension of the Simple Search. It analyzes the search string and brings out all the search keywords separately for a more refined result of your query in a simple search.

API Endpoint

The Analyze API uses the below endpoint:
/analyze

API Method

The Analyze API uses only POST method.

API Request Type

The Analyze API uses JSON request type.

API Request Header

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

API Parameters

To execute Analyze API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
keyword	String	Text query contains entities like job profile, skill, location or organization, etc.	Required

13. Index Count API

This API is used to returns the number of documents indexed.

API Endpoint

The Index Count API uses the below endpoint:
/indexCount

API Method

The Index Count API uses only POST method.

API Request Type

The Index Count API uses JSON request type.

API Request Header

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

14. Suggestions API

This API is used to returns the suggestions for different search fields like JobProfile, Skill, and Degree.

API Endpoint

The Suggestions API uses the below endpoint:
/suggestions

API Method

The Suggestions API uses only POST method.

API Request Type

The Suggestions API uses JSON request type.

API Request Header

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

API Parameters

To execute Suggestions API, the following parameters in the JSON request are needed:

Name	Type	Description	Remarks
indexType	String	Type of the file i.e Resume or JD	Required
keyword	String	Mention the keyword	Required
fieldType	String	Mention the field type like JobProfile/Skill	Required
limit	String	Mention the limit of No. of values to be returned	Required

Search and Match Features

The following topics in this section describe the features of the Search and Match.

A. Geographical Search

This feature is used to find a candidate near you through geographical search in simple and advance search methods.

The search is done using Geocodes/City, State, Country or a distance range. You can select different parameters for measuring the distance range like KM and mile.

The geoSearch is an optional parameter (query) that can be passed in the API request of Simple Search and Boolean Search. Once geoSearch is passed in the request parameter of Simple Search and Boolean Search, it will return the resume/JD that fulfills the geoSearch query.

Request parameters for geoSearch are described below :

Name	Type	Description	Remarks
Option 1
city	string	Name of city	Required
state	string	Name of state related to city	Optional
country	string	Name of Country related to state	Optional
Option 2
longitude	string	Name of city	Required
latitude	string	Name of state related to city	Required
radius	int	Default value is 50	Optional
distanceUnit	string	Default is KM (Kilometer). Possible values are KM and mile	Optional

JSON request with geoSearch parameter (option 1)

"geoSearch": {
    "city": "Pune",
    "state": "Maharastra",
    "country": "India",
    "radius": 50,
    "distanceUnit": "mile"
  }

JSON request with geoSearch parameter (option 2)

"geoSearch": {
    "longitude": "70.255",
    "latitude": "-52.02",
    "radius": 50,
    "distanceUnit": "mile"
  }

B. Facets

Facet is a list of values with the count of documents in which these values are found. Facets are displayed on the left side of the page while searching for Resume’s and JD’s.

The Facet is an optional parameter (query) that can be passed in the API request of Simple Search and Boolean Search. Once Facet is passed in the request parameter of Simple Search and Boolean Search, it will return the list of values with the count of documents in which these values are found.

Facet displays the result as follows :

• Fields : This is displayed as an array (ordered series) of fields as a result of facets.

• Limit : No. of values returns in a facet is 10 by default.

The following are the Facets for the Resume and JD search :

Resume Facets	JD Facets
CurrentJobProfile	JobProfile
PreviousJobProfile	Employer
CurrentEmployer	Degree
PreviousJobProfile	Skill
Degree	TotalExp
Institute	City
Skill	State
TotalExperienceRange	Country
City
State
Country

C. Filter

You can filter Resume and JD search results by selecting further fields in the Facets.

The Filter is an optional parameter (query) that can be passed in the API request of Simple Search and Boolean Search. Once Filter is passed in the request parameter of Simple Search and Boolean Search, it will return the filtered search details.

D. Sorting

You can sort Resume and JD search results by selecting further fields in the sorting parameter.

The sorting is an optional parameter (query) that can be passed in the API request of Simple Search, Boolean Search, and Match. Once sorting is passed in the request parameter of Simple Search and Boolean Search, it will return the resume/JD results that fulfills the sorting query.

The sort parameter arranges search results in either ascending (asc) or descending (desc) order.
When more than one sort criteria is provided, the second entry will only be used if the first entry results in a tie. If there is a third entry, it will only be used if the first and second entries are tied. This pattern continues with further entries.

"sorting":[
      {
        "field" : "Field Name 1",
        "order" : "asc/desc"
      }
	  {
        "field" : "Field Name 2",
        "order" : "asc/desc"
      }
]

The following fields can be used in the sorting (above) parameter :

Resume Sorting Fields	JD Sorting Fields
score	score
ResumeDate	JDDate
ResumeLanguage	JobProfileTitle
ResumeCountry	JobLocationCity
DateOfBirth	JobLocationState
Category	Organization
SubCategory	MinimumYearsExperience
CurrentJobProfile	MaximumYearsExperience
CurrentEmployer	SalaryMinAmount
TotalExperienceInMonths	SalaryMaxAmount
TotalExperienceInYear	TotalExperienceRange
TotalExperienceRange
Institute
City
State
Country
ZipCode

E. Ignore/Exclude Filter

This feature is used to filter the results by ignoring/removing fields as necessary from the result. This feature is used by simply adding ‘-’ (minus symbol) in front of the fields that you want to ignore/remove from the result.

The filter is an optional parameter (query) that can be passed in the API request of Simple Search and Boolean Search. Once this filter is passed in the request parameter of Simple Search and Boolean Search, the response will not contain the fields details that is sent in the request parameter.

JSON request with Ignore/Exclude Filter parameter :

"fitler": {
    "-JobProfile": ["project manager"],
    "-Degree": ["MBA"]
}

F. Pagination

Pagination helps you to fetch data in batches call as a page.

It has page size that means you can customize the number of records you want to fetch in one API call. You can also customize the page number like from where the record should start returning. It is helpful when your search/match query finds a large number of documents.

Request parameters for Pagination are described below :

Name	Type	Description	Remarks
pageStart	Int	Default is 0. This is the start index of record to return.	Optional
pageSize	Int	Default is 50. This is the number of records the is returned in one API call.	Optional

G. Explain Score

This feature is to get a detailed score of search fields that matches with the search result.

Request parameters for Explain Score are described below :

Name	Type	Description	Remarks
explainScore	Boolean	Default is false. If this is set true, it returns the details on how the document is searched.	Optional
explainScoreType	String	Default is text. This can be set as JSON and this returns data only if explainScore parameter is set true.	Optional

H. DeDuplication

Deduplication helps to avoid indexing duplicate records in the search engine.

The Filter is an optional parameter (query) that can be passed in the API request of Parse and Index. Once Deduplication is passed in the request parameter of Parse and Index, it will avoid indexing duplicate records in the search engine.

In Deduplication, you need to set checkDuplicate = true, only then duplicate records will be checked. You can set delicacy checks on field level as well as on output level. By Default if it is on the output level and if no fields are set, then the same output is generated for any record is considered as a duplicate record.

You can check the output with the help of md5 checksum hash code. The other way is to set the fields or the combination of fields to avoid duplicate records. You can set the updated parameter to true to update the records in the existing ID. By default, it is false, means the duplicate records will not be updated and will keep the old value.

Request parameters for Deduplication are described below :

Name	Type	Description	Remarks
Deduplication	Object	Default is false. If this is set true, it returns the details on how the document is searched.	Optional
checkDuplicate	Boolean	True/false	Required
update	Boolean	Default is false that means if duplicate records exist, then the new entry will be ignored. If it is set as true, then the old record will be updated with new data, but it will remain the same.	Optional
Fields	String Array	If it is not set then deduplication will check on output checksum hash code and a list of fields can be set as the combination for deduplication.	Optional

I. Partial Match

Partial Match helps to search the documents based on the words in the keyword.

For example, when you search with keyword Senior Business Consultant, search engine returns documents that contain job profile Senior Business Consultant, Senior Consult, Senior Consultant, Consultant, Business Consultant. Also, search engine returns documents with its matching score based on the search keyword matching partially with Job Profile.

The Partial Match is an optional parameter (query) that can be passed in the API request of Simple Search.

Note:

• In Partial Match, you need to set partialMatch = true, only then partial match records will be returned.

• Partial Match works only on Job Profile.

Request parameters for Partial Match are described below :

Name	Type	Description	Remarks
partialMatch	Boolean	true/false	Required

Search and Match Language Support

RChilli Search and Match supports searching in multiple languages, it does not require any separate configuration. The Search and Match auto-identifies the languages of the Resume/JD and extracts the information.

The Search and Match supports the following languages :

• Dutch

• English

• French

• German

• Italian

• Polish

• Portuguese

• Russian

• Spanish

• Turkish

Search and Match Error Code

Error Code	Error Message
2002	Please provide required input parameters
2004	Content-Type not defined
2005	Not valid Content-Type
2006	indexType must have value either Resume or JD
2008	indexType is required
2010	Invalid Request. Please send valid JSON data
2011	invalid value for id. id must be string value
2012	invalid value for fileName. fileName must be string value
2013	id is required
2014	fileName is required
2015	content is required
2016	commit must have value either true or false
2017	personalInformationIdex should be boolean value
2018	please update value for deDuplication as true/false only
2019	please checkDuplicate value for deDuplication as true/false only
2022	search engine not allowed
2024	please send RChilli resume parser data
2025	please send RChilli JD parser data
2026	invalid base64 content
2027	invalid value for keyword. keyword must be string value
2028	excludeDocumentIds must be a array of string value
2029	sorting must be a array of string value
2030	sorting order must be asc or desc
2031	please provide valid sorting field of JD (score, JobProfileTitle, JobLocationCity, JobLocationState, MinimumYearsExperience, Organization, MinimumYearsExperience, MaximumYearsExperience, SalaryMinAmount, SalaryMaxAmount, Currency, JDDate
2032	please provide valid sorting field of Resume (score, City, State, Country, ZipCode, TotalExperienceInMonths, TotalExperienceInYear, TotalExperienceRange, DateOfBirth, Category, SubCategory, CurrentJobProfile, CurrentEmployer, ResumeDate, ResumeLanguage, ResumeCountry)
2033	geosearch city/geocode is required.
2034	invalid value for distanceUnit. distanceUnit must be either KM or mile.
2035	invalid value for radius
2036	invalid value for latitude. latitude must of string type.
2037	invalid value for longitude. longitude must of string type.
2038	invalid value for geoSearch-city. city must of string type.
2039	invalid value for geoSearch-state. state must of string type.
2040	invalid value for geoSearch-country. country must of string type.
2041	pageStart should be integer value
2042	pageSize should be integer value
2043	explainScore should be boolean value
2044	explainScoreType should be json or text.
2045	partialMatch should be boolean value
2046	facet fields are required.
2047	facet limit should be integer value
2048	please send valid input values for required fields. input values must be array of string type
2049	invalid value for required or optional keyword. optional must be array of string value
2050	invalid value for required or optional keyword. optional must be array of string value
2051	docType must have value either Resume or JD
2052	invalid value for docType. docType must be string type
2053	docType is required
2054	invalid value for jsonData. jsonData must be string type
2055	jsonData is required
2056	invalid base64 content for jsonData
2057	invalid value for matchId. matchId must be array type
2058	matchId is required
2059	please provide matching document id in matchId
2061	invalid value for resumeContent. resumeContent must be string type
2062	invalid value for jdContent. jdContent must be string type
2063	resumeContent is required
2064	jdContent is required
2065	invalid value for resumeFileName. resumeFileName must be string value.
2066	invalid value for jdFileName. jdFileName must be string value
2067	resumeFileName is required
2068	jdFileName is required
2069	matchType is required
2070	matchType must be Resume to JD / JD To Resume
2071	documentId is required
2072	documentId must be a string value
2073	keyword is required
2074	invalid value for fieldType. fieldType must be string value
2075	required field {key} not available. Please provide correct field and in correct format.
2076	optional field {key} not available. Please provide correct field and in correct format.
2077	This field {key} is already used in Required
2078	personalInformationIndex should be boolean value
2079	facet field {key} not available
2081	filter field {filter key} not available. Please provide correct field and in correct format
HTTP Status 405	Request method ‘GET’ not supported

Note: For search engine Index, Search and Match on SubUserlevel Contact support@rchilli.com