Home
API Information
RChilli's API suite enables quick and seamless integration, giving users easy access to all RChilli services. From resume parsing to job management and advanced search, our APIs simplify and automate HR processes, enhancing recruitment efficiency.
Search and Match
The endpoints indicate how you access the resource, while the method indicates the allowed interactions (such as GET, POST, or DELETE) with the resource.
Search and Match Endpoints
This section provides detailed information on the various endpoints available in the Search and Match API.
Delete All Documents
This API is used to delete all indexed files from the database based on the API parameter.

Getting Started
The section guide you through an overview of RChilli and the initial steps for setting up and using the products.
API Information
RChilli's API suite enables quick and seamless integration, giving users easy access to all RChilli services. From resume parsing to job management and advanced search, our APIs simplify and automate HR processes, enhancing recruitment efficiency.
- Resume Parser
  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
  The endpoints indicate how you access the resource, while the method indicates the allowed interactions (such as GET, POST, or DELETE) with the resource.
- Search and Match
  The endpoints indicate how you access the resource, while the method indicates the allowed interactions (such as GET, POST, or DELETE) with the resource.
  - API Authentication
    Search and Match API uses private user key (index key) to authenticate requests. To authenticate the call to an API endpoint, there are only 3 steps:
  - Search and Match Endpoints
    This section provides detailed information on the various endpoints available in the Search and Match API.
    - Parse and Index
      To search resume's and JD's using RChilli Search and Match API, you require to parse the resume/JD and index them.
    - Simple Search
      The Simple Search API method empowers you to make your document searchable with a string query (must contain entities) without specifying search parameters.
    - Free Text Search
      FreeTextSearch method is used to search random text on the indexed Resume or JD.
    - Boolean Search
      In the boolean (advance) search, unlike simple search, you can customize your search by specifying search entities like - Job Profile, Company, Degree, etc. and apply boolean condition as necessary.
    - Match
      This API finds Resumes/Job Descriptions matching your input documents.
    - Match with ID
      This API finds Resumes/Job descriptions matching your input documents ID's.
    - Skill Gap Analysis
      In a Skill Gap Analysis API call, a JD document is matched with a resume, and it returns the matching and the missing skills in the resume.
    - One To One Match
      This API matches resume with JD or JD with Resume and responds the detailed matching score.
    - Match with Multiple Sub-User Ids
      This API finds Resumes/Job descriptions that matches your input documents and provided sub user ids.
    - Check Document Index
      This API is used to check whether a document is indexed or not with given document ID.
    - Get Document Ids
      This API is used to get all the indexed document ID's.
    - Get Document Detail
      This API is used to get a particular indexed document detail by providing document ID.
    - Delete
      This API is used to delete indexed files, from the database, by providing document ID.
    - Delete All Documents
      This API is used to delete all indexed files from the database based on the API parameter.
    - Analyze
      The Analyze query is an extension of the c_RChilli_search_match_API_Endpoints_simple_search.html. 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.
    - Index Count
      This API is used to returns the number of documents indexed for an Index key.
    - Suggestions
      This API is used to returns the suggestions for different search fields like JobProfile and Skill.
    - Spell Checking
      If you give any wrong input while searching, this API will check and correct it.
    - Get Sub User Ids List
      This API returns list of all sub user ID's.
    - Update Index
      The Update Index API allows you to update a block of JSON or a specific entity within a resume or job description (JD) without requiring document parsing through the ResumeParser or JDParser API.
  - Features
    The following topics in this section describe the features of the Search and Match.
  - Response Schema
    The following table describe the Search and Match fields.
  - Request Example
    To get the search and match output data, send a POST request using search and match endpoints, methods, and parameters.
  - Response Example
    Follow the below sample search and match response in the JSON format.
  - 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.
  - Error Code
    This topic lists the error codes of Search and Match Error Code.
- Taxonomy
  The endpoints indicate how you access the resource, while the method indicates the allowed interactions (such as GET, POST, or DELETE) with the resource.
- Resume Redactor
  RChilli Resume Redactor API helps in masking resumes before sending them to the employer.
- Plugins
  The RChilli provides Plugins, such as Resume_Templater_plugin.html, Document_Converter_plugin.html, NER_Tagger_plugin.html, Contact Extractor, GeoLocation_plugin.html, Job_Zone_Plugin.html, and flexisense_requests_plugin_overview.html that extend the capabilities of the RChilli products.
My Account and Features
The My Account application serves as a central hub for users to demo all RChilli API integrations, view API test results, and access their Userkey for authentication.
RChilli Marketplace
The resume parser output can be enriched by activating the other application workflows that are listed on the Enrichment Marketplace such as Lusha, BOLD, Toofr, Rchilli Redact, LLM Parser, etc.
ERP Integration
The components of RChilli application can be integrated with the Oracle HCM Cloud, Oracle PeopleSoft, Salesforce, SAP, and ServiceNow Application.
Release Notes
Release notes comprise new features, improvements, and bug fixes for the following RChilli products.
Glossary
The glossary includes terms and definitions in RChilli Knowledge Center.

Delete All Documents

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

API URL

The Delete All Documents API uses the below URL:

https://searchengine.rchilli.com/RChilliSearchEngineAPI/RChilli/deleteAllDocs

Note: Based on the deleteAllDocument parameter in the API request, the indexed documents are deleted, for more details, refer below API parameter section.

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 Headers


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
indexKey	String	Use your user key as shared by RChilli team	Required
subUserId	String	Your user's unique_ID Note: Make sure that there is no space in your subuser_id	Optional
deleteAllDocument	Boolean	When true: When this parameter is true, all documents indexed on the indexkey and the combination of indexkey + subUserId are deleted (subUserId in the request is not provided). When false: When this parameter is false, or the parameter is not given in the request, then the documents only on that indexkey are deleted, but not the documents which are indexed on the combination of indexkey and subuserId (subUserId in the request is not provided). When the subUserId is given in the request, then the documents which are indexed with the combination of indexKey and subUserId are only deleted. The default value of this parameter is false.	Optional

JSON Request For Delete All Documents

{
    "index": {
        "indexType": "{{Resume or JD}}",
        "indexKey": "{{IndexKey}}"
    },
    "deleteAllDocument": true
}

JSON Response For Delete All Documents - Resume

{
    "status": "200",
    "indexType": "Resume",
    "output": "indexes deleted successfully"
}

Error Code

Table 1. Resume Parser Error Code
Error Code	Error Message
2117	deleteAllDocument parameter value must have either true or false