Integrations, exports and API: what goes in, what comes out.

Sources with a purpose-built reader

These formats have documented readers in Planlined. Other files can use general extraction or AI fallback. Review rates and benefits against the original document; fields and source-page links may be missing or incomplete. Reader availability is not a per-format accuracy benchmark.

See documented capabilities beside the dated workflow evidence, including what the example did not test.

• Medical carrierAetnaFunding Advantage and level-funded quotes
• Medical carrierUnitedHealthcareQuotes and monthly invoices
• Medical carrierFlorida BlueRate sheets and quotes
• Ancillary carriersDental, vision, life, STD and LTDProposals from Principal, Guardian, The Standard, Pacific Life, MetLife, Lincoln Financial, Unum, Cigna, Mutual of Omaha, Aflac, VSP, EyeMed and Delta Dental
• PEOADP TotalSourceProposals and renewal packets
• Payroll and HRISPaychex and AuraAura quote comparisons and HRIS output rate sheets carrying BlueCross Texas, Aetna, UnitedHealthcare, Cigna, Humana and Paychex MEC plans
• Quoting platformBenefitterMulti-carrier proposal exports
• Enrollment materialEmployee benefit guidesPDF and Word open enrollment guides with plan comparison grids
• Rate workbooksExcel and CSV rate gridsRead cell by cell, deterministically, with no model in the loop
• Carrier recognitionIncumbent plan namesCigna, Humana, Kaiser Permanente, Anthem, BlueCross BlueShield, Oscar Health, Molina Healthcare, Centene, Health Net, Ambetter and AvMed are identified from the plan names on incumbent and renewal documents
• Everything elseGeneral readerSBCs, quotes, rate sheets, invoices, census files and benefit summaries from any other carrier. Review is required; extraction can miss or misread values.

Working from a quoting-platform export? Planlined vs Benefitter explains the file-upload handoff, its review requirements and the distinction from a native integration.

Carriers Planlined recognizes by name

The readers above are built for specific document formats. These carriers can be recognized by name wherever they appear, which is what puts the right carrier card, phone number and provider-lookup link into the proposal book and the employee guide. Documents from a carrier without its own reader go through the general reader and land on the same verification screen.

Parsing runs as a job. A request can return the completed result or a job receipt to poll. File size alone does not determine whether the response is immediate.

How it connects across your stack

A REST API at app.planlined.com with API keys, signed outbound webhooks, and connector adapters. Confirm workspace access, provider availability, permissions and setup before connecting an external system. The OpenAPI document is available on request.

See documented capabilities beside the dated workflow evidence, including what the example did not test.

• AuthenticationBearer tokens or API keys with scopesSign in tokens and Planlined OAuth access tokens as bearer, or an X-API-Key header generated in workspace settings. Keys carry scopes such as cases:read, cases:import, exports:write and pdf:extract. Partner apps can also obtain tokens through Planlined's own OAuth token endpoint, with secret rotation.
• WorkflowsOne capabilities endpoint, five workflowsGET /api/v1/integrations/capabilities returns the endpoints, scopes and retry policy for parse, case import, benefit guide publishing, proposal book PDF and proposal book workbook. Long jobs expose status, result and cancel. Requests accept an X-Idempotency-Key so a retried call cannot create a duplicate.
• ParsingSend a document, get structured plansPOST /api/v1/parse/unified runs the same reader registry the app uses. Parsing is submitted as a job. The request may wait for completion or return a job id to poll; callers can request an asynchronous response. Type-specific routes exist for census, quote, SBC, invoice, spreadsheet, image and XML.
• Case importPush a packet in, get a case or a proposed mergePOST /api/v1/case-imports retains every source file, parses all plans and benefit types, and either creates a case or proposes a version-guarded merge into an existing one. Automatic mode commits only when every benefit maps unambiguously; review mode waits for a person. Retained sources can be reprocessed later.
• ExportsArtifacts your system can fetchProposal book PDF and XLSX, hosted benefit guide links, JSON, and versioned artifact downloads. Render endpoints take the artifact content the app produces; they do not yet render from a bare case id.
• LimitsDocumented, not surprisingIntegration routes allow 60 requests a minute per key; webhook management routes allow 30. Files are capped at 50 MB. The unified route waits up to 45 seconds for a submitted job unless an asynchronous response is requested. This is a response-wait budget, not a guaranteed completion time.