Stop building isolved integrations from scratch. Bindbee gives you a single API to sync employee data, benefits enrollments, dependent information, and more—without the maintenance headaches.
Bindbee normalizes isolved's data into our unified models. One integration, consistent data structure across 60+ HR systems.
Your customer authenticates their isolved account through Magic Link—our drop-in, secure auth component. No isolved credentials touch your servers.
We pull data from isolved and normalize it to unified models. Initial sync completes in minutes, then automatic incremental syncs keep everything fresh.
One REST API for isolved and 60+ other HR systems. Same endpoints, same data models, regardless of which HRIS your customer runs.
Customers authenticate effortlessly via Magic Link, with an embeddable SDK that enables seamless, in-app connections.
Most customers complete setup in under 10 minutes. Your end-user authenticates via Magic Link, and initial data sync begins immediately. No engineering effort required on your side beyond the initial Bindbee integration.
Yes. Enable include_custom_fields=true in your API requests. Custom fields appear in the custom_fields object with their original isolved field names, so you can access any data isolved exposes beyond Bindbee's unified models.
Yes. Bindbee provides full benefits coverage from isolved including the Benefit, Employer Benefit, Dependent, and Dependent Benefit models. You get plan names, contribution amounts, coverage tiers, dependent demographics, and enrollment dates—everything you need for census data or eligibility verification.
After initial sync, Bindbee runs automatic incremental syncs. Frequency depends on your plan. You can also trigger manual syncs via the API or dashboard at any time.
Bindbee caches synced data, so your API calls continue working even during isolved outages. We retry failed syncs automatically and notify you of persistent issues via webhooks.
Yes. Use query parameters like employment_status, modified_after, employee_id, and page_size to filter API responses. For benefits, filter by employee_id, employer_benefit_id, or date ranges using start_date_from and start_date_to.
Yes. Configure webhooks to receive notifications when connector syncs complete, employee data changes, or sync errors occur. See our webhooks documentation.
You don't need to worry about it. Bindbee manages rate limiting with isolved's API internally. We cache data and handle retries automatically, so you never hit throttling issues.
Bindbee syncs data periodically, not in real-time. For most use cases—benefits administration, census generation, eligibility checks—near-real-time data synced every few hours is more than sufficient. Webhooks notify you when fresh data is available.
Bindbee handles version differences internally. Our unified API returns consistent data regardless of which isolved configuration or modules your customer runs.
