Connect Sapling

Sapling (also known as Kallidus) is an HRIS integration that syncs employee, job, and compensation data to Pave using an API key.

Before you connect

• You must be a Sapling administrator to generate an API key.
• You will need your Sapling URL (for example, your-company.saplingapp.io). The company ID is the first part of your Sapling URL, before .saplingapp.io.
• Sapling API keys expire every 90 days. When a key expires, you will need to generate a new one and resubmit it in Pave.

Connect Sapling to Pave

1. In Sapling, follow these instructions from Sapling to generate an API key.
2. Copy the API key.
3. In Pave, go to Connections and find Sapling.
4. Paste the API key into the field provided.
5. Enter your Sapling URL (for example, your-company.saplingapp.io). Do not include https:// or a trailing slash.
6. Click Submit.
7. Go to Connections and verify the Sapling integration shows as In sync.

Troubleshooting

"Hostname/IP does not match certificate's altnames" error The company ID was likely entered incorrectly. Make sure the Sapling URL does not include .sapling.com or .saplingapp.io twice. The URL should be in the format your-company.saplingapp.io.

401 error after the integration was previously working Sapling API keys expire every 90 days. Generate a new API key in Sapling and resubmit it in Pave.

Data is missing or incomplete Pave filters out inactive employees and employees without a work email address. If specific employees are missing, confirm they are active in Sapling and have a company email on file.

Fields that sync

Custom mappings may apply to your account.

• First name, last name, preferred name
• Work email
• Ethnicity, date of birth
• Job title, department, division
• Employment type
• Manager name, manager email
• Start date, termination date
• Location (city, state, country, zip code)
• Base pay, currency, pay frequency
• Variable pay
• Bonus
• Signing bonus
• Commission

Additional data

• Compensation history: Not supported via this integration. You can manually upload historical compensation data to Pave.
• Custom fields: Not supported.
• Benefits: Not supported via this integration. You can manually upload benefits data to Pave.