Stop building PlanSource integrations from scratch. Bindbee gives you a single API to sync benefits enrollments, employee data, dependents, and more—without the maintenance headaches.
Bindbee normalizes PlanSource's data into our unified models. One integration, consistent data structure across 60+ HRIS and benefits platforms.
Authenticate via Magic Link—our drop-in auth component. Your customer connects their PlanSource account in minutes.
We normalize PlanSource data to unified models with automatic incremental syncs. Benefits, employees, dependents—all standardized.
One REST API for PlanSource and 60+ other HR and benefits systems.
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.
Yes. Enable include_custom_fields=true in your API requests. Custom fields appear in the custom_fields object with their original PlanSource field names.
Yes. The Benefit model shows employee benefit enrollments including plan name, coverage tier, benefit plan category, effective dates, and provider information. Dependent enrollments are also available via the Dependent Benefit model.
Yes. The Dependent model includes dependent name, relationship (spouse, child), date of birth, and SSN. The Dependent Benefit model shows which benefits cover each dependent, including plan details and effective dates.
Yes. The Employer Benefit model contains plan-level details including plan_name, provider_name, benefit_plan_category, and available coverage_tiers.
After initial sync, Bindbee runs incremental syncs automatically. Frequency depends on your plan. You can also trigger manual syncs via the API or dashboard.
Bindbee caches synced data, so your API calls continue working. We retry failed syncs automatically and notify you of persistent issues via webhooks.
Yes. Bindbee is SOC 2 Type II certified, HIPAA compliant, and GDPR ready. Data is encrypted in transit and at rest. We never store customer credentials.
Yes. Configure webhooks to receive notifications when connector syncs complete, employee data changes, or sync errors occur. See our webhooks documentation.
Bindbee uses cursor-based pagination. Each response includes a cursor value—pass it in your next request to get the next page. Use page_size (max 100) to control results per page.
