Skip to main content
Use these names when making requests to our API to specify the integration you want to connect to.

​
HRIS (Human Resource Information Systems)

  • 7Shifts: seven_shifts
  • ADP Workforce Now: adp
  • ADP Workforce Now (SFTP): adp_sftp
  • BambooHR: bamboohr
  • BreatheHR: breathehr
  • BSwift (SFTP): bswift_sftp
  • CharlieHR: charliehr
  • Darwin Box: darwin_box
  • Dayforce: dayforce
  • Deel: deel
  • Deputy: deputy
  • Ease (SFTP): ease_sftp
  • Employee Navigator (SFTP): employee_navigator_sftp
  • Employment Hero: employment_hero
  • Factorial: factorial
  • Google Workspace: google-workspace
  • Hibob: hibob
  • HR Partner: hrpartner
  • HRWorks: hrworks
  • Humaans: humaans
  • iSolved (SFTP): isolved_sftp
  • Keka HR: keka
  • Microsoft Entra ID: microsoft_entra_id
  • Nmbrs: nmbrs
  • Okta: okta
  • Opportune HR: opportunehr
  • Oracle HCM: oracle_hcm
  • Paychex: paychex
  • Paychex Flock (SFTP): paychex_flock
  • Paycom: paycom
  • Paycom (SFTP): paycom_sftp
  • Paycor: paycor
  • Paylocity: paylocity
  • Paylocity (SFTP): paylocity_sftp
  • PeopleStrong: peoplestrong
  • Personio: personio
  • Plansource (SFTP): plansource_sftp
  • Prime: prime
  • Prism: prism
  • Quickbooks: quickbooks
  • Rippling: rippling
  • Rippling (SFTP): rippling_sftp
  • Sage HR: sage-hr
  • SAP SuccessFactors: sap-success-factors
  • Sesame: sesame
  • TriNet HR: trinet_hr
  • UKG Pro: ukg-pro
  • UKG Ready: ukg-ready
  • Workday: workday
  • Workday RaaS: workday_raas
  • Workline: workline
  • Xero: xero
  • Xero (AU): xero_au
  • Zoho People: zoho-people

​
ATS (Applicant Tracking Systems)

  • Ashby: ashby
  • BambooHR: bamboohr
  • Greenhouse: greenhouse
  • JazzHR: jazzhr
  • JobScore: jobscore
  • Jobvite: jobvite
  • Lever: lever
  • Paylocity Recruiting: paylocity_recruiting
  • Recruitee: recruitee
  • SAP SuccessFactors: sap-success-factors
  • Teamtailor: teamtailor
  • Workable: workable
  • Workday: workday

​
LMS (Learning Management Systems)

  • SAP SuccessFactors: sap_sf_lms
  • Workday: workday

​
How to Use

When generating a link_token, specify the desired integration by using the appropriate name from the lists above. For example, if you want to integrate with BambooHR for HRIS, use the name bamboohr in your request.

​
Example

Here’s an example of a request payload to generate a link_token for integrating with BambooHR as an HRIS: 
{
  "end_user_data": {
    "org_name": "Acme Corp.", // Unique entity name of your customer's organisation
    "origin_id": "064e1cd7-49ad-4e6d-8005-7e4c92fe9675" // Unique ID to Identify your customer's organisation
  },
  "category": "HRIS", // category
  "integration": "bamboohr" // Integration name
}
For ATS integration with Greenhouse, use the name green-house: 
{
  "end_user_data": {
    "org_name": "Acme Corp.", // Unique entity name of your customer's organisation
    "origin_id": "064e1cd7-49ad-4e6d-8005-7e4c92fe9675" // Unique ID to Identify your customer's organisation
  },
  "category": "ATS", // category
  "integration": "greenhouse" // Integration name
}
For LMS integration with Workday, use the name workday: 
{
  "end_user_data": {
    "org_name": "Acme Corp.", // Unique entity name of your customer's organisation
    "origin_id": "064e1cd7-49ad-4e6d-8005-7e4c92fe9675" // Unique ID to Identify your customer's organisation
  },
  "category": "LMS", // category
  "integration": "workday" // Integration name
}
By using the correct names, you can seamlessly connect with the desired HRIS or ATS through Bindbee’s Unified APIs.