Darwinbox ATS API Integration

These are the list of integration use cases supported by Knit for Darwinbox ATS API as part of the ATS category

POST Add Tags to Candidate Profile V3

ID: post_add_tags_to_candidate_profile_v3
Operation: write
Entities: tag, candidate
Summary: The POST Add Tags to Candidate Profile V3 API allows users to add preconfigured custom tags to candidate profiles. The request requires a list of candidate IDs and the custom tags to be added. The request must include a Content-Type header set to application/json. The response returns a status, a message indicating the success of the operation, and additional data confirming the tags were added successfully.
Input Fields: Input Fields
Output Fields: Output Fields

ID: post_archive_requisition
Operation: write
Entities: employee, requisition
Summary: The POST Archive Requisition API allows users to archive or delete a requisition in the Darwinbox system. It requires a requisition ID and the employee ID of the requester. Optionally, a reason for the archive/delete and a bypass span can be provided. The API uses Basic Auth for authentication and expects a JSON payload. Upon success, it returns a status, message, and the requisition ID.
Input Fields: Input Fields
Output Fields: Output Fields

ID: post_create_requisition
Operation: write
Entities: requisition, job detail, position detail
Summary: The Create Requisition API allows users to create a new requisition in the Darwinbox system. It requires various parameters such as auto_approve, requisition_created_by, and bypass_span. The request body includes detailed information about the requisition, including basic details, job details, position details, and other optional details. The response returns a status, message, and a list of requisition IDs.
Input Fields: Input Fields
Output Fields: Output Fields

ID: post_fetch_candidate_data_bulk_v3
Operation: read
Entities: candidate, job, application
Summary: The POST Fetch Candidate Data - Bulk V3 API allows users to retrieve bulk candidate data from the Darwinbox platform. The API supports optional parameters such as candidate_id, job_id, created_from, created_to, updated_from, and updated_to to filter the data. The request must include a Content-Type header set to application/json. The response includes a status, message, and a list of candidate data, each containing details like unique_id, candidate_id, firstname, lastname, email, phone, job_id, status, source_type, source_name, tags, created_date, and application_data with biographical, contact, work experience, references, and professional references information.
Input Fields: Input Fields
Output Fields: Output Fields

ID: post_fetch_job_detail_v3
Operation: read
Entities: job, department, location
Summary: The Fetch Job Detail V3 API is used to retrieve detailed information about a specific job using the job's unique identifier. The API requires a job ID as a mandatory parameter in the request body. The request must include a Content-Type header set to application/json. The response includes a status code, a message, and detailed job information such as job title, department, designation, salary range, experience requirements, location, and more. It also provides information about the hiring lead and applicant fields. The API uses Basic Authentication with a username and password.
Input Fields: Input Fields
Output Fields: Output Fields

ID: post_fetch_job_list_v3
Operation: read
Entities: job, department, location
Summary: The Fetch Job List V3 API allows users to retrieve a list of jobs from the Darwinbox platform. The API requires a POST request to the specified endpoint. Optional parameters include the group company and a timestamp to filter jobs updated after a certain date. The response includes a status, message, and a list of job details such as job ID, code, title, department, location, and employment type.
Input Fields: Input Fields
Output Fields: Output Fields

ID: post_reject_candidate_v3
Operation: write
Entities: rejection reason, job, candidate
Summary: The POST Reject Candidate V3 API allows users to reject candidates by providing a list of candidate IDs. The request requires a list of candidate IDs in the request body. The API uses Basic Auth for authentication, requiring a username and password. The response includes a status code, a message indicating the success of the operation, and details about the rejected candidate.
Input Fields: Input Fields
Output Fields: Output Fields