Available Connectors
Taleo ATS Integration
Taleo connector for Kombo’s ATS API
This connector is in closed beta. Please contact us to get access.
The Taleo ATS integration allows you to sync ATS data between Taleo and your application through Kombo’s unified API. The tool slug for this connector is taleo.
Guides and Resources
Supported Features & Coverage
Jobs
Jobs
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| job_code | |
| description | |
| status | |
| category | |
| department | |
| post_url | |
| salary_currency | |
| salary_period | |
| location | |
| remote_created_at | |
| remote_updated_at |
Candidates
Candidates
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| first_name | |
| last_name | |
| phone_numbers | |
| email_addresses | |
| social_media | |
| location | |
| remote_created_at | |
| remote_updated_at |
Application Stages
Application Stages
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| global_index |
Applications
Applications
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| outcome | |
| current_stage_id | |
| job_id | |
| candidate_id | |
| screening_question_answers | |
| remote_updated_at |
Screening questions
Screening questions
Screening questions are always marked as not required, since on the API, there is no indication of whether they are required or not. In our testing, submissions were successful while submitting no questions.
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description | |
| format |
Job-specific screening questions
Job-specific screening questions
| Field | Notes |
|---|---|
| index | |
| required | |
| precondition_question_id | |
| precondition_options | |
| job_id | |
| question_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Jobs
Jobs
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| job_code | |
| description | |
| status | |
| category | |
| department | |
| post_url | |
| salary_currency | |
| salary_period | |
| location | |
| remote_created_at | |
| remote_updated_at |
Candidates
Candidates
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| first_name | |
| last_name | |
| phone_numbers | |
| email_addresses | |
| social_media | |
| location | |
| remote_created_at | |
| remote_updated_at |
Application Stages
Application Stages
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| name | |
| global_index |
Applications
Applications
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| outcome | |
| current_stage_id | |
| job_id | |
| candidate_id | |
| screening_question_answers | |
| remote_updated_at |
Screening questions
Screening questions
Screening questions are always marked as not required, since on the API, there is no indication of whether they are required or not. In our testing, submissions were successful while submitting no questions.
| Field | Notes |
|---|---|
| id | |
| remote_id | |
| changed_at | |
| remote_deleted_at | |
| title | |
| description | |
| format |
Job-specific screening questions
Job-specific screening questions
| Field | Notes |
|---|---|
| index | |
| required | |
| precondition_question_id | |
| precondition_options | |
| job_id | |
| question_id | |
| id | |
| changed_at | |
| remote_deleted_at |
Create candidate
Create candidate
| Input Field | Notes |
|---|---|
| candidate.first_name | |
| candidate.last_name | |
| candidate.email_address | |
| candidate.phone_number | |
| candidate.location.city | |
| candidate.availability_date | |
| candidate.social_links.url | |
| application.job_id | |
| screening_question_answers.question_id | |
| screening_question_answers.answer | |
| attachments.name | |
| attachments.data | |
| attachments.data_url | |
| source.name |
Create application
Create application
| Input Field | Notes |
|---|---|
| candidate.first_name | |
| candidate.last_name | |
| candidate.email_address | |
| candidate.phone_number | |
| candidate.location.city | |
| candidate.availability_date | |
| candidate.social_links.url | |
| application.job_id | |
| screening_question_answers.question_id | |
| screening_question_answers.answer | |
| attachments.name | |
| attachments.data | |
| attachments.data_url | |
| source.name |
Get application attachments
Get application attachments
| Input Field | Notes |
|---|---|
| application_id |
Get candidate attachments
Get candidate attachments
The endpoint we are using returns the attachments of all applications of a candidate. It however does not return the ID/Number of the applications.
| Input Field | Notes |
|---|---|
| candidate_id |
| Feature | Notes |
|---|---|
| Source Writing | |
| Sync Only Created Applications | |
| Connection Guide | |
| API Passthrough | |
| Scope Testing |