Build on it / Integration gateway
Signed events out, scoped keys in
The Integration Gateway connects your own systems to Waypoint: signed webhooks the moment something happens, a partner API behind scoped keys, and an event stream a partner reads on from where it left off.
Example: your finance system receives a signed message the moment a payment is issued, then reads the payment details through the partner API under a key scoped to payments.
The question this answers
What is connected to our data, and what may it do?
Every key carries its own scopes, every endpoint its own secret, and every delivery is recorded. A key reaching outside its scopes is listed while the platform is in observe mode and refused once it is switched to enforce — so the inventory is a page, not an archaeology project.
Three ways your systems connect
Out, in, and the stream
Webhooks Out
Up to 10 endpoints per organization, each message signed with an HMAC of its body. Claim created, status changed, payment issued, SIU referral opened, quote responded and policy bound.
Partner API Keys In
Up to 10 keys per organization, each with chosen scopes, an optional daily limit and a burst guard of 120 requests a minute by default that can be changed but never removed.
The Event Stream
Every claim and payment event is written to your organization’s stream, which a partner reads on from the last event it saw.
Feeds Through The Same Doors
Bank check-status feeds and electronic vendor invoices come in through the same keyed doors, and agency systems send submissions under a gateway key.
The rules
What the gateway enforces
A webhook problem never stops the claim or payment that caused it.
Rule
Detail
Addresses
https and public only — no private, local or cloud-metadata targets, no redirects — checked at registration and again at delivery
Contents
Identifiers, statuses and amounts only
Delivery
Up to 5 attempts, retried after 1, 5, 30 and 60 minutes, then marked dead; every delivery recorded
Scopes
Claims, one claim, payments, the document list, contacts and the event stream, each behind its own scope
Retention
Stream rows follow the retention of the records they belong to
Entitlement
integration.gateway
Where we are honest
Integration is still a project
A gateway makes connections governable. It does not make them trivial.
Mapping Is Real Work
Your systems’ fields differ from ours. Mapping is done once per connection, and it is a scoped project, not a switch.
Your Endpoint Must Cope With Repeats
A message can arrive more than once after a retry. Build your receiver to recognise one it has already handled.
Partner Reliability Is Theirs
The gateway records failures and marks dead deliveries. It cannot make an unreliable endpoint reliable.
Read next
List what you are connected to today
If that list takes more than an hour to produce, the gateway is solving a problem you already have.