Submit enrollments in your native HRIS / payroll shape. A saved mapping transforms each record into the canonical schema before the normal pipeline runs. Use this if you’d rather not re-shape data in your own code.
Create a mapping from 1–10 sample records. Claude proposes the transform rules; the platform contract-tests the result before returning. High-confidence proposals with clean contract tests auto-confirm; lower-confidence ones are saved as drafts for admin review. You can also POST a hand-written mapping directly instead of sample_records.
Related: GET /mappings, GET/PATCH/DELETE /mappings/:id, POST /mappings/:id/test, POST /mappings/:id/chat (preview-only AI edit), POST /mappings/:id/chat/apply, and GET/POST /mappings/:id/versions for history and rollback.
GET /inbox
Aggregated rejections, mapping errors, and shape-drift warnings, each with an AI-proposed fix attached. Resolve individual items via POST /inbox/:id/resolve.
Public endpoint — no API key required. Creates a carrier account, mints a crr_-prefixed API key (shown once), and returns the next onboarding step. Rate-limited to 3 attempts per minute per IP.
Follow-ups use the returned key: GET /carrier/me, POST /carrier/companion-guide (AI parses rules), PUT /carrier/transport (SFTP / API creds), and POST /carrier/sandbox — three clean sandbox runs auto-promote the carrier to ACTIVE.
Additional endpoints:GET /enrollments/:id, POST /enrollments/:id/retry, GET /batches/:id/content (fetch your stored 834), GET /analytics/dashboard, POST /webhooks/test. All endpoints return JSON. Errors follow RFC 7807 problem-details format.
03 Carrier integration
40 carriers pre-mapped.
Velora EDI supports SFTP, AS2, and REST API transmission methods. Each carrier connection is configured with companion-guide rules that enforce carrier-specific validation. Pre-mapped carriers include UnitedHealthcare, Cigna, Aetna, every Blue Cross plan, Kaiser Permanente, Humana, MetLife, Guardian, and more.
Companion guides can be uploaded as PDFs — our AI parses carrier-specific rules automatically and applies them during validation. New carriers self-onboard via POST /api/v1/carrier/signup and reach production status in under an hour after three clean sandbox runs.
All PHI is encrypted at rest (AES-256-GCM) and in transit (TLS 1.2+). API keys are hashed with SHA-256 and never stored in plaintext. Rate limiting is enforced per-client via distributed Redis. Hash-chained audit logs capture every PHI access with IP, user ID, and timestamp.
Business Associate Agreement (BAA) is part of paid signup. See /baa for the full agreement, /security for the technical posture, and /hipaa for the compliance pillars.
Need more depth?
The OpenAPI 3.1 spec, TypeScript SDK type stubs, and webhook signing playground are all on the docs landing.