> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kombo.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# SmartRecruiters ATS Integration
> SmartRecruiters connector for Kombo's ATS API
The SmartRecruiters ATS integration allows you to sync ATS data between SmartRecruiters and your application through Kombo's unified API. The tool slug for this connector is `smartrecruiters`.
## Guides and Resources
Step-by-step instructions to connect your SmartRecruiters account to Kombo.
Learn how to set up candidate sources in SmartRecruiters.
How to view and manage candidate sources in SmartRecruiters.
Additional documentation and guides for SmartRecruiters.
Additional documentation and guides for SmartRecruiters.
## Supported Features & Coverage
SmartRecruiters does not validate email addresses. Kombo will sync all users, but only return emails that have been validated.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| first\_name | |
| last\_name | |
| email | |
| status | |
| remote\_data | |
| Field | Notes |
| -------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| job\_code | |
| description | |
| employment\_type | |
| status | |
| visibility | |
| category | |
| department | |
| post\_url | |
| experience\_level | |
| salary\_amount\_from | |
| salary\_amount\_to | |
| salary\_currency | |
| salary\_period | |
| location | |
| custom\_fields | |
| integration\_fields | |
| remote\_url | |
| opened\_at | |
| remote\_created\_at | |
| remote\_updated\_at | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| title | |
| description\_html | |
| status | |
| visibility | |
| url | |
| job\_id | |
| remote\_data | |
| remote\_created\_at | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| first\_name | |
| last\_name | |
| company | |
| title | |
| source | |
| phone\_numbers | |
| email\_addresses | |
| social\_media | |
| location | |
| custom\_fields | |
| integration\_fields | |
| remote\_url | |
| remote\_created\_at | |
| remote\_updated\_at | |
| remote\_data | |
SmartRecruiters will continue to reference inactive or deleted application stages
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| global\_index | |
| Field | Notes |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| outcome | |
| rejection\_reason\_name | |
| rejected\_at | |
| current\_stage\_id | |
| job\_id | |
| candidate\_id | |
| screening\_question\_answers | |
| custom\_fields | |
| integration\_fields | |
| remote\_url | |
| remote\_created\_at | The remote\_created\_at field will only be filled when we are syncing the application status history which we are doing to sync rejected\_at. |
| remote\_updated\_at | The remote\_updated\_at field will only be filled when we are syncing the application status history which we are doing to sync rejected\_at. Furthermore, it only reflects changes to the application status, not the application itself. |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| title | |
| description | |
| format | |
| category | |
SmartRecruiters API only provides access to tags that are currently assigned to candidates. This means Kombo can only retrieve tags that are attached to specific candidates, rather than providing a complete list of all available tags in the SmartRecruiters system.
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| title | |
| starting\_at | |
| ending\_at | |
| location | |
| application\_id | |
| canceled | |
| remote\_data | |
| Field | Notes |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| status | |
| application\_id | The SmartRecruiters offer model only contains references to the candidate and job. If `application_id` is enabled in your Kombo scope config, we therefore additionally request the application read scope to retrieve the application ID from the candidate and job. |
| custom\_fields | |
| integration\_fields | |
| remote\_created\_at | |
| remote\_updated\_at | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| name | |
| remote\_data | |
| Field | Notes |
| ------------------- | ----- |
| id | |
| remote\_id | |
| changed\_at | |
| remote\_deleted\_at | |
| remote\_label | |
| scope | |
| unified\_type | |
| Field | Notes |
| ------------------- | ----- |
| candidate\_id | |
| tag\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
| Field | Notes |
| ------------------- | ----- |
| index | |
| job\_id | |
| stage\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
| Field | Notes |
| -------------------------- | ----- |
| index | |
| required | |
| precondition\_question\_id | |
| precondition\_options | |
| job\_id | |
| question\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
Smartrecruiters exposes a list of hiring team members with a specific role
* **HIRING\_MANAGER** (shown as "Hiring Manager" in the UI) maps to unified type `HIRING_MANAGER`
* **RECRUITER** (shown as "Recruiter" in the UI) maps to unified type `RECRUITER`
* **INTERVIEW\_TEAM** (shown as "Interviewer" in the UI) maps to unified type `INTERVIEWER`
* **COORDINATOR** (shown as "Coordinator" in the UI) maps to unified type `COORDINATOR`
* **EXECUTIVE** (shown as "Executive" in the UI) has no unified type
* Other role values (often a custom id) have no unified type
| Field | Notes |
| ------------------- | ----- |
| job\_user\_id | |
| role\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
| Field | Notes |
| ------------------- | ----- |
| roles | |
| job\_id | |
| user\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
Each user has **systemRole.id**; Kombo stores that value on the role. Custom ids use the name from the synced system-roles resource when available, otherwise the raw id.
* **ADMINISTRATOR** maps to unified type `ADMIN`
* **EMPLOYEE**, **STANDARD**, and **EXTENDED** have no unified type
* **RESTRICTED** corresponds to the Basic role in the SmartRecruiters UI and has no unified type
* Any other **systemRole.id** follows the custom-role lookup above and has no unified type.
| Field | Notes |
| ------------------- | ----- |
| user\_id | |
| role\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
| Field | Notes |
| ------------------- | ----- |
| interview\_id | |
| user\_id | |
| id | |
| changed\_at | |
| remote\_deleted\_at | |
The `read_jobs` permission is required because we need to look up job posting details when creating candidates. SmartRecruiters does not allow setting a stage directly when creating a candidate. Passing the `stage_id` parameter to Kombo when creating a candidate will therefore move the candidate to the stage post-creation, and requires the `candidate_manage` SmartRecruiters permission. Past candidate experience must be defined with a start date and title within the SmartRecruiters API. Kombo will set the title to '-' if only the company field is passed without a title. The start date is set to 2100-01-01 as a dummy value; if you require a different start date, please set it via remote\_fields.
| Input Field | Notes |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| candidate.first\_name | |
| candidate.last\_name | |
| candidate.email\_address | |
| candidate.company | |
| candidate.title | |
| candidate.phone\_number | |
| candidate.location.city | |
| candidate.location.country | |
| candidate.social\_links.url | |
| application.job\_id | |
| application.stage\_id | |
| screening\_question\_answers.question\_id | |
| screening\_question\_answers.answer | |
| attachments.name | |
| attachments.content\_type | |
| attachments.data\_url | |
| attachments.data | |
| attachments.type | |
| source.name | Please note that we can only write sources that your customer has already set up with the exact name (under `www.smartrecruiters.com/settings/configuration/custom-sources`). If you specify a source within the `source.name` field, we will only use it if it's already set up within SmartRecruiters and is of the type 'OTHER'. Otherwise, the source defined in the connection flow is used. |
| source.unified\_key | |
| source.id | |
| gdpr\_consent.given | |
The `read_jobs` permission is required because we need to look up job posting details when creating candidates. SmartRecruiters does not allow setting a stage directly when creating a candidate. Passing the `stage_id` parameter to Kombo when creating a candidate will therefore move the candidate to the stage post-creation, and requires the `candidate_manage` SmartRecruiters permission. Past candidate experience must be defined with a start date and title within the SmartRecruiters API. Kombo will set the title to '-' if only the company field is passed without a title. The start date is set to 2100-01-01 as a dummy value; if you require a different start date, please set it via remote\_fields.
| Input Field | Notes |
| ----------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| candidate.first\_name | |
| candidate.last\_name | |
| candidate.email\_address | |
| candidate.company | |
| candidate.title | |
| candidate.phone\_number | |
| candidate.location.city | |
| candidate.location.country | |
| candidate.social\_links.url | |
| application.job\_id | |
| application.stage\_id | |
| screening\_question\_answers.question\_id | |
| screening\_question\_answers.answer | |
| attachments.name | |
| attachments.content\_type | |
| attachments.data\_url | |
| attachments.data | |
| attachments.type | |
| source.name | Please note that we can only write sources that your customer has already set up with the exact name (under `www.smartrecruiters.com/settings/configuration/custom-sources`). If you specify a source within the `source.name` field, we will only use it if it's already set up within SmartRecruiters and is of the type 'OTHER'. Otherwise, the source defined in the connection flow is used. |
| source.unified\_key | |
| source.id | |
| gdpr\_consent.given | |
| Input Field | Notes |
| ------------- | ----- |
| candidate\_id | |
| tag.name | |
| Input Field | Notes |
| ------------- | ----- |
| candidate\_id | |
| tag.name | |
The SmartRecruiters 'add attachment to candidate' endpoint is deprecated. Please prefer to use Kombo's 'add attachment to application' endpoint.
| Input Field | Notes |
| ------------------------ | ----- |
| application\_id | |
| attachment.name | |
| attachment.content\_type | |
| attachment.data\_url | |
| attachment.data | |
| attachment.type | |
| Input Field | Notes |
| --------------- | ----- |
| application\_id | |
| stage\_id | |
| Input Field | Notes |
| --------------------- | ----- |
| application\_id | |
| rejection\_reason\_id | |
| Input Field | Notes |
| ------------------------ | ----- |
| application\_id | |
| label | |
| url | |
| details.attributes.key | |
| details.attributes.value | |
| Input Field | Notes |
| --------------- | ----- |
| application\_id | |
| content | |
| Input Field | Notes |
| --------------- | ----- |
| application\_id | |
| Input Field | Notes |
| ------------- | ----- |
| candidate\_id | |
The SmartRecruiters 'add attachment to candidate' endpoint is deprecated. Please prefer to use Kombo's 'add attachment to application' endpoint.
| Input Field | Notes |
| ------------------------ | ----- |
| candidate\_id | |
| attachment.name | |
| attachment.content\_type | |
| attachment.data\_url | |
| attachment.data | |
| attachment.type | |
| Input Field | Notes |
| ------------------------ | ----- |
| candidate\_id | |
| label | |
| url | |
| details.attributes.key | |
| details.attributes.value | |
| Feature | Notes |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Source Writing | |
| Sync Only Created Applications | |
| Connection Guide | |
| Prerequisites | |
| Candidate source tracking | |
| Candidate Cutoff Filtering | |
| Roles | |
| System roles (e.g. Admin) | Each user has **systemRole.id**; Kombo stores that value on the role. Custom ids use the name from the synced system-roles resource when available, otherwise the raw id. |
* **ADMINISTRATOR** maps to unified type `ADMIN`
* **EMPLOYEE**, **STANDARD**, and **EXTENDED** have no unified type
* **RESTRICTED** corresponds to the Basic role in the SmartRecruiters UI and has no unified type
* Any other **systemRole.id** follows the custom-role lookup above and has no unified type. |
\| Job roles (e.g. Hiring Manager) | Smartrecruiters exposes a list of hiring team members with a specific role
* **HIRING\_MANAGER** (shown as "Hiring Manager" in the UI) maps to unified type `HIRING_MANAGER`
* **RECRUITER** (shown as "Recruiter" in the UI) maps to unified type `RECRUITER`
* **INTERVIEW\_TEAM** (shown as "Interviewer" in the UI) maps to unified type `INTERVIEWER`
* **COORDINATOR** (shown as "Coordinator" in the UI) maps to unified type `COORDINATOR`
* **EXECUTIVE** (shown as "Executive" in the UI) has no unified type
* Other role values (often a custom id) have no unified type |
\| OAuth | |
\| API Passthrough | |
\| Webhook Subscriptions | application.created: triggered when an application was created application.fields.updated: triggered when application fields were updated application.onboarding-status.updated: triggered when application onboarding status was updated application.screening-answers.created: triggered when screening question answers were added to an application application.screening-answers.updated: triggered when screening question answers were updated on an application application.source.updated: triggered when the source of the application was updated application.status.updated: triggered when the status (stage) of an application was changed candidate.created: triggered when a candidate was created candidate.updated: triggered when a candidate was updated including tag assigned/unassigned interview\.created: triggered when an interview was scheduled interview\.updated: triggered when an interview was updated candidate.deleted: triggered when a candidate was deleted interview\.canceled: triggered when an interview was canceled job.ad.created: triggered when a job ad was created job.ad.updated: triggered when a job ad was updated job.ad.postings.updated: triggered when the postings of a job ad were updated, including job ad being published or unpublished job.created: triggered when a job was created job.hiring-team.updated: triggered when the hiring team was updated on a job job.status.updated: triggered when the status of a job was updated job.updated: triggered when a job was updated offer.created: triggered when an offer was created offer.updated: triggered when an offer was updated Not covered: screening questions were updated for a job |
\| Automatic Setup | |
\| Scope Testing | |
\| Delta Syncs | |
\| Custom Field Explorer | |
\| Candidates | |
\| EEO Questions | |
## Integration Variants
**Current connector:** SmartRecruiters
For **SmartRecruiters**, we also offer the following other connector variants:
SmartRecruiters for the Assessment category