Brokers and MGAs send their own payload to one InsOps endpoint. PolicyCenter receives a submission in the format it expects, and carriers add distribution partners without new IT work.
The Problem
Insurance data migrations are slow and expensive
Every sender builds its own connector
PolicyCenter exposes APIs, so each broker, MGA and TPA writes a small module that maps its data and calls them. Each build takes months of engineering, and none of it includes security, auditing or monitoring. The carrier answers every sender’s questions one at a time before a single submission arrives.
One change reaches every sender
When a carrier changes an endpoint or Guidewire ships a release, every connector built against it has to change too. A carrier working with 50 senders must notify, support and retest all 50 for a single change. Submissions slow while senders rework their modules, and carrier IT loses time it planned for other work.
Growth waits on IT capacity
Each new distribution partner needs carrier IT time for credentials, payload questions and testing. That work grows with every partner, so carriers cap how many they onboard. Fewer partners means fewer submissions reaching underwriters, and less premium written.
How does InsOps Help?
How Yazh (Yaal) Moves Submissions Into PolicyCenter
Self-Service Sign-Up
A partner registers with a one-time password, receives an API username and key, and selects the lines of business it will send.
LiLa-Suggested Mapping
The partner uploads a sample JSON payload. LiLa maps source fields to PolicyCenter fields and lists the ones it could not match for a person to resolve.
Value Translation
Source values become PolicyCenter codes, so a partner’s “Commercial Property” arrives as the code your instance expects.
Test Before Live
Partners run submission clearance, account creation and submission creation in a test environment, then check the result in PolicyCenter.
Incomplete Payloads Returned
A payload with gaps goes back to the sender to complete instead of reaching your queue.
Changes Handled Once
When PolicyCenter or a carrier endpoint changes, InsOps updates the mapping in one place. A new mandatory field raises an alert, and a default value keeps submissions moving.
FAQ