canonical: https://jentic.com/apis/plansource.com/plansource-benefits-api # PlanSource Benefits Administration API PlanSource is a cloud-based benefits administration platform serving HR departments, brokers, and insurance carriers. The Administrative API provides comprehensive control over employee enrollment workflows, coverage management, payroll deduction calculations, and Evidence of Insurability (EOI) submissions. HR teams use it to sync employee demographics from HRIS systems, automate open enrollment periods, manage qualifying life events, and generate compliance reports for ACA, COBRA, and HIPAA. The API supports batch operations for high-volume subscriber imports, coverage updates during acquisition integrations, and bulk termination processing. It enables benefits administration to operate as part of a unified HR technology stack, connecting PlanSource with payroll systems, time tracking tools, and employee self-service portals. ## For AI agents Manage employee benefits enrollment, coverage, payroll deductions, and EOI submissions through PlanSource's benefits administration platform. ## Scope Provides benefits administration and enrollment management. Does not handle employee time tracking, performance reviews, or core HRIS functions-use dedicated HR platforms. Does not process insurance claims-use carrier APIs. ## Capabilities - Sync employee demographics and subscriber information from HRIS systems - Manage benefits coverage including elections, enrollments, and qualifying life events - Calculate and export payroll deductions for enrolled benefits - Submit and track Evidence of Insurability (EOI) applications for medical underwriting - Generate ACA compliance reports including 1095-C forms and affordability calculations - Perform batch operations for subscriber imports, coverage updates, and terminations - Manage administrator accounts with role-based permissions for brokers and HR staff ## Use cases ### HRIS Integration and Demographic Synchronization HR operations teams integrate PlanSource with platforms like Workday, BambooHR, and ADP to maintain single-source-of-truth employee data. The API enables bidirectional sync where new hires flow from HRIS to PlanSource for benefits enrollment, while enrollment elections flow back for payroll deduction setup. Automated sync jobs run nightly to update demographic changes like addresses, dependents, and employment status. This eliminates dual data entry, reduces enrollment errors, and ensures benefit eligibility rules always evaluate against current employee attributes. Example prompt: Fetch new employees from HRIS API who started in past 24 hours, create subscriber records in PlanSource with demographics and employment data, trigger new hire enrollment workflow. ### Open Enrollment Automation and Reporting Benefits administrators orchestrate annual open enrollment using the API to monitor completion rates, send reminder notifications, and generate executive dashboards. The API provides endpoints to list subscribers who haven't completed enrollment, retrieve their current elections, and track benefit plan participation rates. Automated workflows use this data to trigger personalized reminder emails through marketing automation platforms. Post-enrollment, the API generates summary reports for insurance carrier submissions and payroll system imports. Example prompt: Query PlanSource for all active subscribers without completed enrollment for current period, export list with contact information, generate enrollment completion report showing plan participation by department. ### Payroll Integration and Deduction Management Payroll teams use the API to retrieve employee benefits deductions for each pay period and import them into payroll systems. The API calculates deductions based on enrollment elections, pay frequency, and contribution amounts, handling scenarios like new enrollment proration and mid-month coverage changes. For companies with multiple payroll calendars (salaried, hourly, commission), the API supports filtering deductions by employee group and pay schedule. This ensures accurate benefit premiums are withheld and remitted to carriers on time. Example prompt: Retrieve payroll deductions for all subscribers for upcoming pay date, group by payroll calendar, format for payroll system import, validate total deduction amounts against carrier invoices. ### Compliance Reporting for ACA and Government Regulations HR compliance teams use the API to generate Affordable Care Act (ACA) reports including 1095-C forms, measurement period calculations, and affordability safe harbor analysis. The API aggregates enrollment data, hours worked, and premium contributions to determine full-time employee status and offer compliance. It also supports COBRA continuation coverage tracking and HIPAA special enrollment period validation. Automated compliance workflows pull data monthly to identify at-risk scenarios before IRS filing deadlines. Example prompt: Generate ACA compliance report for tax year covering all full-time employees, calculate affordability percentages, identify employees not offered minimum essential coverage, export data for 1095-C form generation. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/subscriber` | Create or update subscriber demographic information | | GET | `/subscriber/{subscriber_id}/coverage` | Retrieve coverage elections for a subscriber | | GET | `/payroll/deductions` | Get payroll deductions for a pay period | | POST | `/eoi/application` | Submit an Evidence of Insurability application | | GET | `/aca/enrollees` | Retrieve ACA enrollment data for compliance reporting | ## Key resources - **Subscribers** — Manage employee and dependent demographic information. - **Coverage** — Track benefit plan enrollments and elections. - **Payroll Deductions** — Calculate and export employee benefit deductions. - **EOI Applications** — Submit and track Evidence of Insurability requests. - **ACA Reports** — Generate Affordable Care Act compliance data. ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 62 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 87 / 100 - Developer Experience & Jentic Compatibility: 61 / 100 - AI-Readiness & Agent Experience: 43 / 100 - Agent Usability: 92 / 100 - Security: 68 / 100 - AI Discoverability: 55 / 100 - **View full report:** https://jentic.com/apis/plansource.com/plansource-benefits-api/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the PlanSource Benefits Administration API by hand means learning its bearer token auth and hand-building requests across its subscriber, coverage, payroll-deduction and enrollment endpoints yourself. Through Jentic you install once, import PlanSource from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** PlanSource puts the subscriber id in the URL path (`/subscriber/{subscriber_id}/coverage`), so a rule can pin your agent to one subscriber: it reads that subscriber's coverage and nothing else. You choose the operations it may call, so state-changing ones like creating a subscriber or submitting an EOI application are not included unless you add them. - **Credential handling:** Your PlanSource token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get an employee's benefits enrollments' or 'read payroll deductions', and Jentic returns the matching PlanSource operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ADP Workforce Now API** — ADP provides payroll and HR management with benefits administration capabilities. - **Gusto Embedded Payroll API** — A Gusto alternative for running payroll and managing employee benefits, positioned against PlanSource's benefits administration platform. ## FAQ ### What authentication does the PlanSource API use? The PlanSource Administrative API uses Bearer token authentication. You obtain API credentials from your PlanSource account administrator and pass the token in the Authorization header for all requests. ### Can I automate open enrollment workflows with the PlanSource API? Yes. The API provides endpoints to monitor enrollment completion, retrieve pending enrollments, update employee elections, and generate participation reports. You can build automated reminder workflows and track completion rates programmatically. ### How do I integrate PlanSource with my payroll system? Use the payroll deductions endpoints to retrieve calculated benefit premiums for each pay period. The API supports filtering by pay schedule and employee group, returning deduction data in formats compatible with most payroll systems for import. ### What is Evidence of Insurability (EOI) and how does the API handle it? EOI is medical underwriting required for certain coverage amounts (like high-value life insurance). The API allows submitting EOI applications with medical questionnaires, tracking approval status, and receiving carrier decisions-automating a traditionally paper-based process. ### How do AI agents use the PlanSource API through Jentic? Agents search Jentic for tasks like 'sync employee benefits enrollments' and receive PlanSource operation schemas. Jentic securely stores API credentials and handles authentication, enabling agents to query enrollments, calculate deductions, and generate reports with natural language parameters. ### Can I limit what my agent is allowed to do with the PlanSource Benefits Administration API? Yes. Because you run Jentic One yourself, your own rules decide which PlanSource operations and credentials the agent can use. Since the API carries the subscriber id in the URL path, such as `/subscriber/{subscriber_id}/coverage`, you can pin the agent to a single subscriber so it reads that person's coverage and nothing else. You also choose the exact operations it may call, so state-changing ones like creating a subscriber or submitting an EOI application stay off unless you add them.