Partners and API / Integration gateway
One way in, and it remembers what came through
A single gateway for inbound and outbound integration, with credentials that are never returned, payloads that are validated, and every exchange recorded.
Integrations accumulate quietly. A gateway exists so that in three years somebody can still answer what is connected and what it is allowed to do.
Review an integrationWhat is connected to our data, and what may it do?
A question most operations cannot answer after two years of point-to-point integrations. Every connection goes through the gateway with its own credential and its own scope, and every exchange is recorded — so the inventory is a query rather than an archaeology project.
Scoped, validated, recorded
How a connection is governed
- 01
One gateway, not point-to-point
Inbound and outbound traffic passes a single controlled surface, so there is no side channel that grew out of a one-off project.
- 02
Credentials are write-only
Once saved, an integration credential is never returned to any screen or API response. Support cannot read your carrier password back to you, because nothing can.
- 03
Scope is explicit
A connection carries its own entitlements. An integration built for bordereaux cannot read claim notes because nobody scoped it to.
- 04
Exchanges are recorded
What was sent, what was received, what was rejected. A carrier dispute about a transmission is settled from the record.
The integration inventory
What runs through the gateway
Each of these is a real lane rather than a category, and each carries its own scope and its own record.
| Lane | Direction and purpose |
|---|---|
| Bordereaux exchange | Outbound and inbound, scheduled, in the carrier’s format |
| Bulk FNOL | Inbound claim feeds from carrier systems |
| Inbound email | Documents and notices arriving by mail into intake |
| Third-party data | Outbound lookups, with responses recorded |
| Sanctions screening | Outbound checks, results and overrides on the party |
| Partner API | Inbound programmatic access, entitlement-scoped |
Integration is still a project
A gateway makes connections governable. It does not make them trivial, and vendors implying otherwise cause most integration overruns.
Mapping is real work
Every carrier format differs. Mapping is done once per partner and it is a scoped project, not a switch.
No marketplace of pre-built connectors
We do not have a catalog of turnkey carrier integrations. Ask what exists before assuming yours is covered.
Partner reliability is theirs
The gateway records failures and surfaces rejections. It cannot make an unreliable partner endpoint reliable.